I have certain patch to apply in my system, but unfortunately adpatch is coming out with following error for any patch.
Determining valid on-site files...
AutoPatch error:
The following file is missing:
..........appl/alr/11.5.0/admin/driver/alrfile.drv
AutoPatch error:Error reading product file driver files complete; make tapes
AutoPatch error:Error determining valid on-site files
You should check the file..........................appl/admin/SID/log/logfile.log for errors.
===============================
No answer in metalink for this. I did find for alrfile.drv in my system and did found the file in $APPL_TOP/amf/alr/11.5.0/admin/driver/alrfile.drv, just created softlink for alr under $APPL_TOP like
ln -s amf/alr alr
and reapplied the patch and it worked.
Happy Troubleshooting !!!
Friday, February 27, 2009
Thursday, February 26, 2009
IDM version 10.1.4.3
Those who were waiting for IDM version 10.1.4.3 here is some good news for them. IDM version 10.1.4.3 (7215628) has been released and it has recently got certified with EBS 11i. Metalink Note 743141.1 and 233436.1 has more information on the same
Although we decided not to upgrade as off now. But if get chance will test and upload results for WNA setup.
Happy Troubleshooting !!!
Although we decided not to upgrade as off now. But if get chance will test and upload results for WNA setup.
Happy Troubleshooting !!!
Tuesday, February 17, 2009
Changing Data Guard Protection level
We are in process of testing Data Guard setup. While doing that I come across a situation where I have to change Protection status from status from Maximum Performance to Maximum Availability:
On Primary:
alter system set log_archive_dest_2='SERVICE=Instance_Name LGWR SYNC AFFIRM valid_for=(ONLINE_LOGFILES,PRIMARY_ROLE) db_unique_name=SID;
alter system set log_archive_dest_state_2=enable;
Shutdown and mount the primary and standby database:
SQL> -- [Connect to the primary database]
SQL> SHUTDOWN IMMEDIATE
SQL> STARTUP MOUNT
SQL> -- [Connect to the standby database]
SQL> ALTER DATABASE RECOVER MANAGED STANDBY DATABASE CANCEL;
SQL> SHUTDOWN IMMEDIATE
SQL> STARTUP NOMOUNT
On Primary
ALTER DATABASE SET STANDBY DATABASE TO MAXIMIZE AVAILABILITY;
On Standby
ALTER DATABASE RECOVER MANAGED STANDBY DATABASE DISCONNECT FROM SESSION;
On Primary
ALTER DATABASE OPEN;
SQL> SELECT PROTECTION_MODE, PROTECTION_LEVEL, DATABASE_ROLE FROM V$DATABASE;
Happy Troubleshooting !!!
On Primary:
alter system set log_archive_dest_2='SERVICE=Instance_Name LGWR SYNC AFFIRM valid_for=(ONLINE_LOGFILES,PRIMARY_ROLE) db_unique_name=SID;
alter system set log_archive_dest_state_2=enable;
Shutdown and mount the primary and standby database:
SQL> -- [Connect to the primary database]
SQL> SHUTDOWN IMMEDIATE
SQL> STARTUP MOUNT
SQL> -- [Connect to the standby database]
SQL> ALTER DATABASE RECOVER MANAGED STANDBY DATABASE CANCEL;
SQL> SHUTDOWN IMMEDIATE
SQL> STARTUP NOMOUNT
On Primary
ALTER DATABASE SET STANDBY DATABASE TO MAXIMIZE AVAILABILITY;
On Standby
ALTER DATABASE RECOVER MANAGED STANDBY DATABASE DISCONNECT FROM SESSION;
On Primary
ALTER DATABASE OPEN;
SQL> SELECT PROTECTION_MODE, PROTECTION_LEVEL, DATABASE_ROLE FROM V$DATABASE;
Happy Troubleshooting !!!
Monday, February 16, 2009
Forgotten wallet manager password
We all know that wallet is secured with password. We need password to opne wallet and include some more certificates or for some admin work. But what if we forgot its password. Can we reset its password ? Answer is NO. So please do remember this wallet manaager password otherwise you have to redo all your work for wallet.
As per Metalink Note : 367755.1
"Unfortunately there is nothing that can be done here.
If the Wallet password is lost, a new Wallet and Certificate Request need to be created. Then a new certificate from this Certificate Request would need to be generated, and then imported to the new wallet."
Happy Troubleshooting !!!
As per Metalink Note : 367755.1
"Unfortunately there is nothing that can be done here.
If the Wallet password is lost, a new Wallet and Certificate Request need to be created. Then a new certificate from this Certificate Request would need to be generated, and then imported to the new wallet."
Happy Troubleshooting !!!
Tuesday, January 13, 2009
BIB-7000 Cannot access X Server
Kindly attention !! This is not repeat of post, something new in stores.
If you have checked my earlier post regarding the same error I hope issue might have resolved for you. Even if it doesn't I have something new today, which will help not to use DISPLAY setting at all for Jserv.
If problem still exists when using VNC or Xvfb with JDK 1.4.2 or 1.5, proceed with instructions for setup below:
You are using J2SE 1.4.2 or J2SE 1.5 (this feature is not available in JDK 1.3.1)
You have jserv_ux_ias1022.properties version 15.80.115105.2 or higher. (patch TXK (FND) AUTOCONFIG TEMPLATE ROLLUP PATCH L (NOV 2005) or higher deliver support for this new feature)
The setting controlling the 'Headless' support for J2SE in the jserv.properties is the following: wrapper.bin.parameters=-Djava.awt.headless=[truefalse]
By default this is set to 'false'.
To change this to 'true' and thus enabling the 'Headless' support feature perform the following steps:
Use context-editor to change value for %s_java_awt_headless% to 'true'
Run Autoconfig to recreate the configuration files
Verify that now the above mentioned setting in jserv.properties is set to 'true'
Run the AOLJ test "X Server Accessibility" and verify it shows the success message
Remarks:
The DISPLAY setting is not used anymore when 'Headless' support is enabled. This Note only applies to Jserv. Non-java tools like Reports 6i may still require the X-server to be available in the environment.
Happy Troubleshooting !!!
If you have checked my earlier post regarding the same error I hope issue might have resolved for you. Even if it doesn't I have something new today, which will help not to use DISPLAY setting at all for Jserv.
If problem still exists when using VNC or Xvfb with JDK 1.4.2 or 1.5, proceed with instructions for setup below:
You are using J2SE 1.4.2 or J2SE 1.5 (this feature is not available in JDK 1.3.1)
You have jserv_ux_ias1022.properties version 15.80.115105.2 or higher. (patch TXK (FND) AUTOCONFIG TEMPLATE ROLLUP PATCH L (NOV 2005) or higher deliver support for this new feature)
The setting controlling the 'Headless' support for J2SE in the jserv.properties is the following: wrapper.bin.parameters=-Djava.awt.headless=[truefalse]
By default this is set to 'false'.
To change this to 'true' and thus enabling the 'Headless' support feature perform the following steps:
Use context-editor to change value for %s_java_awt_headless% to 'true'
Run Autoconfig to recreate the configuration files
Verify that now the above mentioned setting in jserv.properties is set to 'true'
Run the AOLJ test "X Server Accessibility" and verify it shows the success message
Remarks:
The DISPLAY setting is not used anymore when 'Headless' support is enabled. This Note only applies to Jserv. Non-java tools like Reports 6i may still require the X-server to be available in the environment.
Happy Troubleshooting !!!
Subscribe to:
Posts (Atom)