Document ID: 282253
http://support.veritas.com/docs/282253
E-Mail this document to a colleague
http://support.veritas.com/docs/282253
E-Mail this document to a colleague
How to change the stored Oracle password within Symantec Indepth for Oracle 6.2.x
Exact Error Message
ORA-01017: invalid username/password; logon denied
ORA-01017: invalid username/password; logon denied
Details:
Download Now - 4 K
File Name: change_pass_282253.zip
File Type: Utility
Click Below to Browse the FTP files by Product:
ftp.support.veritas.com/pub/support/products
I. Introduction
Several i3 components require the ability to log into the Performance Warehouse. The Indepth for Oracle component requires the ability to log into the monitored Oracle instance. If any of the passwords for these Oracle accounts have been changed, the corresponding i3 component needs to be notified of the new password. This TechNote describes how to perform this update.
If running i3 7.x, refer to TechNote http://library.veritas.com/docs/282252
II. Procedure
1. Download the attached change_pass_282253.zip file
2. Unpack it in a convenient temporary location
3. Copy the enclosed change_pass.jar file to <i3_root>/java/1.3.1/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 -[a|p|o] <oracle_server> <oracle_sid> <new_password>
The first argument is defined as follows:
-a: when changing the Oracle database password used by the Alerts FocalPoint
-p: when changing the Oracle database password used by the i3 Performance Warehouse process
-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 on the Performance Warehouse:
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
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:
Several i3 components require the ability to log into the Performance Warehouse. The Indepth for Oracle component requires the ability to log into the monitored Oracle instance. If any of the passwords for these Oracle accounts have been changed, the corresponding i3 component needs to be notified of the new password. This TechNote describes how to perform this update.
If running i3 7.x, refer to TechNote http://library.veritas.com/docs/282252
II. Procedure
1. Download the attached change_pass_282253.zip file
2. Unpack it in a convenient temporary location
3. Copy the enclosed change_pass.jar file to <i3_root>/java/1.3.1/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 -[a|p|o] <oracle_server> <oracle_sid> <new_password>
The first argument is defined as follows:
-a: when changing the Oracle database password used by the Alerts FocalPoint
-p: when changing the Oracle database password used by the i3 Performance Warehouse process
-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 on the Performance Warehouse:
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
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 the <pw_host_name>
- Use the <port> value for the <pw_port>
- Use the <db-name> for the <pw_sid>
Download Now - 4 K
File Name: change_pass_282253.zip
File Type: Utility
Click Below to Browse the FTP files by Product:
ftp.support.veritas.com/pub/support/products
Supplemental Material:
| System: Ref.# | Description |
| Error Code: 01017 | invalid username/password; logon denied |
Products Applied:
Indepth for Oracle 6.2, 6.2.1
Inform for Alerts 6.2, 6.2.1
i3 6.2, 6.2.1
Indepth for Oracle 6.2, 6.2.1
Inform for Alerts 6.2, 6.2.1
i3 6.2, 6.2.1
Last Updated: April 21 2006 06:42 PM GMT
Expires on: 365 days from publish date
Subscribe to receive critical updates about this document
Expires on: 365 days from publish date
Subscribe to receive critical updates about this document
Subjects:
i3
How To Question: Perf Warehouse Configuration
Indepth for Oracle
How To Question: Product Configuration
Inform for Alerts
How To Question: General Question
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)
English (US)
Operating Systems:
Windows 2000
Windows 2000
Advanced Server SP2, Advanced Server SP3, Advanced Server SP4, Advanced Server Windows Powered SP2, Advanced Server Windows Powered SP3, Advanced Server Windows Powered SP4, Datacenter Server SP2, Datacenter Server SP3, Datacenter Server SP4, Professional SP2, Professional SP3, Professional SP4, Server SP2, Server SP3, Server SP4, Server Windows Powered SP2, Server Windows Powered SP3, Server Windows Powered SP4
AIX
4.3, 5.1ML03, 5.2
HP-UX
10.2, 11.0, 11.11
Solaris
2.6, 7.0, 8.0, 9.0
Linux
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, 4.0 Workstation SP6a
Windows Server 2003
DataCenter, Enterprise Server, Standard Server, Storage Server, Web Server
Windows Small Business Server 2003
Premium Edition, Standard Edition
Symantec World Headquarters:
20330 Stevens Creek Blvd. Cupertino, CA 95014
World Wide Web: http://www.symantec.com,
Tech Support Web: http://entsupport.symantec.com,
E-Mail Support: http://seer.entsupport.symantec.com/email_forms,
FTP: ftp://ftp.entsupport.symantec.com or http://ftp.entsupport.symantec.com
20330 Stevens Creek Blvd. Cupertino, CA 95014
World Wide Web: http://www.symantec.com,
Tech Support Web: http://entsupport.symantec.com,
E-Mail Support: http://seer.entsupport.symantec.com/email_forms,
FTP: ftp://ftp.entsupport.symantec.com or http://ftp.entsupport.symantec.com
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.