000027932 - KB-1533 How to capture 5.0 Oracle install log information

Document created by RSA Customer Support Employee on Jun 14, 2016Last modified by RSA Customer Support Employee on Apr 21, 2017
Version 2Show Document
  • View in full screen mode

Article Content

Article Number000027932
Applies ToAffected Versions: 5.0.1; 5.0
Resolution

The current ACM 5.0 installation process loses the Oracle logging information after the installation (for both failure or success) due to the fact that Oracle deletes the log file. This is not a crucial problem for a successful installation, but can be problematic on a failed installation, especially when trying to diagnose possible causes for that failure.


 


Until Oracle provides a method to retain this log, the current workaround is as follows:


 


1st - Make use of the system 'check' script provided with the installation files BEFORE the installation is started. This script, InspectSystem.sh, is referenced in the 5.0 ACM Installation guide as being located in /home/oracle/deploy, however if the installation fails this directory does not exist. Also, you will want to run this script before you install the product. This script can be found after the main aveksa-5.0.bz2 file is untar'd into /tmp/aveksa/staging (the default staging location), in the


/tmp/aveksa/staging/deploy/ directory.


 


 


2nd - If the Oracle installation log information needs to be captured, this can be done by making use of the unix 'tail -f ' command. The Oracle installation will create a directory in /tmp with a name format of: OraInstall<date-timestamp>, and in that directory a log file, named installActions<date-timestamp>. log will be created. To 'capture' this log information, two putty/terminal sessions should be opened. If using putty, ensure that the window lines of scrollback exceed 200000 (to ensure all data is captures.. the default size is 200lines and this is not a large enough buffer.) If using another terminal session, ensure that the window display buffer is significantly large.


 


From one terminal/putty window, set the default directory as /tmp. From the 2nd window, start the ACM installation. Continue to monitor the contents of /tmp from the first window, and as soon as the OraInstall<date-timestamp> directory is created, monitor IT's contents for the installActions<date-teimsampt>.log file creation. As soon as THAT file appears, make use of the unix tail -f command to start displaying it's contents. You can also use the unix > command to send that terminal output to a file, but note that in this case you will not see any messages displayed in this terminal window. Examples of both are shown below.


 


$ cd /tmp


$ ls


$ cd OraInstall2011-09-23_04-21-47PM


$ tail -f installActions2011-09-23_04-21-47PM.log


or


$ tail -f installActions2011-09-23_04-21-47PM.log > /tmp/acm_5_ora.log


 


At ACM installation completion or failure, send the appropriate log files to Aveksa Techincal Support.


If the log information has been sent to the terminal, copy that output to a file and send it. If the output has been re-directed to /tmp/acm_5_ora.log, send that file to support.


 


 


 


 


Update 11/09/2011


 


Attached to this Knowledgebase solution is a simple script, which can be copied to a 5.0 or 5.0.1 system and executed any time before or during an ACM 5.0.x installation. It should be executed BEFORE the start of the Oracle Install component. The script monitors the system for the start of the Oracle installation and copies the Oracle install log when it's found, to /tmp/aveksa/oracle.log so that the user does not have to 'watch' for this file and tail -f it during the installation process. The script exits at the completion of the ACM install process.


 


Script name: 5_0_install_captureOraclelog.sh


 


Note that this a similiar script is being added to ACM versions 5.1+. The deletion of the oracle install log file is a known Oracle 11g installation issue, which Oracle will address. (we do not have a date/version for this from Oracle at this time).


 


Note if this script is downloaded to a Windows system and then moved to the Unix system, the file permissions and type should be modified to ensure correct operation. After copying to the Unix system, do the following:


 


$ dos2unix 5_0_install_captureoraclelog.sh


$ chmod 755 5_0_install_captureoraclelog.sh

Attachments

    Outcomes