adpreclone fails via crontab script but succeeds when run manually

Observed Error:

There is already an ACTIVE ADOP CYCLE with session id : SP2-0640: Not connected adpreclone cannot be run with pending ADOP session

Fix:

As per the cause mentioned in Adpreclone.pl Fails with an SP2-0640 Error on 12.2 Application Tier ( Doc ID 2139174.1 ) – “Sqlplus permits user variable lengths up to 240 characters.”, there seems to be a restriction at OS level that is causing only script to fail only on PROD and not non-PROD.

  1. Verified and Patch 22271970 was already applied.
  2. Modified the script to assign apps and weblogic passwords directly into the variables.
Unknown's avatar

Published by heemasatapathy

Heema is an Oracle Ace Pro, IEEE Senior Member, and experienced speaker at both local and international IT conferences. With two decades of hands-on experience as a senior DBA and Solution Architect, Heema is adept at database administration and eager to embrace new technologies. Known for being customer-focused, organized, and self-motivated, Heema has a strong track record in managing technical projects and communicating solutions effectively. His global IT experience spans India, Japan, Malaysia, Singapore, Switzerland, and the USA. He holds a Bachelor of Engineering degree with Honors.

Leave a comment