adpatch is Failing to Pass Parameters Correctly to pnupgvpp.sql and pnupgpro.sql
VPC Member opened this thread for the customer.
We are applying a merged patch that includes 387 patches including 5591144, 3653484, 9845801, and 6168505.
There are several cases where adpatch is not passing parameters correctly to .sql scripts. There are 9 "pn" scripts that have problems including the 2 in the problem summary, plus paupg103.sql and apupgsec.sql.
The adworker log contains the following.
sqlplus -s APPS/***** @/oracleapp3/apptst/CGFSTST/appl/pn/11.5.0/patch/115/sql/pnupgvpp.sql 26 32
Enter value for 3:
As you can see, it is only passing 26 and 32 to the script. It should be passing PN 1000 26 32. There are no errors. It just hangs.
The script listed in the logs varies, but the error is always the same - "Enter value for 3:" or sometimes "Enter value for 1:".
We are applying a merged patch that includes 387 patches including 5591144, 3653484, 9845801, and 6168505.
There are several cases where adpatch is not passing parameters correctly to .sql scripts. There are 9 "pn" scripts that have problems including the 2 in the problem summary, plus paupg103.sql and apupgsec.sql.
The adworker log contains the following.
sqlplus -s APPS/***** @/oracleapp3/apptst/CGFSTST/appl/pn/11.5.0/patch/115/sql/pnupgvpp.sql 26 32
Enter value for 3:
As you can see, it is only passing 26 and 32 to the script. It should be passing PN 1000 26 32. There are no errors. It just hangs.
The script listed in the logs varies, but the error is always the same - "Enter value for 3:" or sometimes "Enter value for 1:".
Tagged:
0