How to change the stored Oracle password within Symantec Indepth for Oracle 7.x
Details:
I. IntroductionSeveral i3 components require
the ability to log into the Performance Warehouse database. The Indepth
for Oracle component requires the ability to log into the monitored Oracle
instance. If any of the passwords for these Oracle accounts are changed,
the corresponding i3 component needs to be notified of the new
password. This TechNote describes how to perform this update..
If
running i3 6.x, refer to
TechNote
http://support.veritas.com/docs/282253
.
II. Procedure
1. Download the
attached change_pass_282252.zip file
2. Unpack it in a convenient temporary
location
3. Copy the enclosed change_pass.jar file to
<i3_root>/java/1.4.2/lib/
4. Copy the enclosed
change_pass.sh (or .bat on Win32) to <i3_root>
5.
From the <i3_root> directory, run the script (.sh or .bat) using
the following syntax:
change_pass.sh -[p|o]
<oracle_server> <oracle_sid>
<new_password>
The first argument is defined as
follows:
-p: when changing the Oracle database password used by
Alerts or Performance Warehouse
-o: when changing the Oracle database
password used by Indepth for Oracle on the monitored instance
As an
example, here is the command to change the password used by the Performance
Warehouse Focal Point:
change_pass.sh
-p OracleServer OracleSID NewPaSSw0rd
Note: The
<oracle_server> and
<oracle_sid> values need to be the
values as displayed in AdminPoint.
6. Using AdminPoint, restart the
appropriate i3 component that was changed. If the -p parameter was used,
make sure to restart the Alerts FocalPoint as well
7. If the database
password was changed for the Performance Warehouse Oracle user, in addition to
running the command line change above, each Indepth for Oracle schema must be
updated to rebuild the pss_pw_link that is used to connect that instance to the
Performance Warehouse.
Use the following syntax to recreate the database
link:
create
database link pss_pw_link connect to <pw user id> identified by <pw
user pass> using
'(DESCRIPTION=(ADDRESS_LIST=(ADDRESS=(PROTOCOL=TCP)(Host=<pw host
name>)(Port=<pw port>)))(CONNECT_DATA=(SID=<pw
sid>)))'
Use appropriate values for <pw_user_id>,
<pw_user_pass>, <pw_host_name>, <pw_port>, <pw_sid>.
These values can be found in
<i3_root>/products/i3fp/registry/connection-pools/jdbc/pools.xml.
- Use
the <user> value for <pw_user_id>
- Use
the <host> value for <pw_host_name>
- Use
the <port> value for <pw_port>
- Use
the <db-name> value for
<pw_sid>
Download Now - 4 K
File Name: change_pass_282252.zip
File Type: Utility
Click Below to Browse the FTP files by Product:
ftp.support.veritas.com/pub/support/products
Products Applied:
Indepth for Oracle 7.1, 7.5
Inform for Alerts 7.1, 7.5
i3 7.1, 7.5
Subjects:
i3
How To Question: Perf Warehouse Configuration
Indepth for Oracle
How To Question: Product Configuration
Inform for Alerts
How To Question: General Question
Languages:
English (US)
Operating Systems:
Windows 2000Advanced Server, Advanced Server Windows Powered, Datacenter Server, Professional, Server, Server Windows Powered
AIX
4.3, 5.1, 5.2, 5.3
TRU64
4.0D, 5.0, 5.1
HP-UX
11.0, 11.0/64bit, 11i v2 (IA64), 11i v2 (PA-RISC)
Solaris
2.5, 2.6, 7.0, 8.0, 9.0
Linux
RHEL 3.0 (AS, ES, WS), RedHat 6.2, RedHat 7.0, RedHat 7.1, RedHat 7.2, RedHat Enterprise Server 2.1 (AS, ES, WS)
Windows NT
4.0 Server SP6a
Windows XP
5.2, Pro 5.1
Windows Server 2003
DataCenter, Enterprise Server, Standard Server, Storage Server
Windows Small Business Server 2003
Premium Edition, Standard Edition
THE INFORMATION PROVIDED IN THE SYMANTEC SOFTWARE KNOWLEDGE BASE IS PROVIDED "AS IS" WITHOUT WARRANTY OF ANY KIND. SYMANTEC SOFTWARE DISCLAIMS ALL WARRANTIES, EITHER EXPRESS OR IMPLIED, INCLUDING THE WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. IN NO EVENT SHALL SYMANTEC SOFTWARE OR ITS SUPPLIERS BE LIABLE FOR ANY DAMAGES WHATSOEVER INCLUDING DIRECT, INDIRECT, INCIDENTAL, CONSEQUENTIAL, LOSS OF BUSINESS PROFITS OR SPECIAL DAMAGES,EVEN IF SYMANTEC SOFTWARE OR ITS SUPPLIERS HAVE BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. SOME STATES DO NOT ALLOW THE EXCLUSION OR LIMITATION OF LIABILITY FOR CONSEQUENTIAL OR INCIDENTAL DAMAGES SO THE FOREGOING LIMITATION MAY NOT APPLY.