Password Reset

[Former Member]

Hi All,

We recently implemented password change policy in our portal system with AIX and DB2 Database.

at OS Level i changed passwords of <SID>ADM and DB2<SID>.

By mistake i have changed password of the SAP<SID>DB Password at OS level, It should be changed by Configtool.

i am unable to login to Configtool and gives error as below...

com.sap.engine.frame.core.configuration.ConfigurationException: Error while connecting to DB.

at com.sap.engine.core.configuration.impl.persistence.rdbms.DBConnectionPool.createConnection(DBConnectionPool.java:365)

at com.sap.engine.core.configuration.impl.persistence.rdbms.DBConnectionPool.<init>(DBConnectionPool.java:130)

at com.sap.engine.core.configuration.impl.persistence.rdbms.PersistenceHandler.<init>(PersistenceHandler.java:38)

at com.sap.engine.core.configuration.impl.cache.ConfigurationCache.<init>(ConfigurationCache.java:149)

at com.sap.engine.core.configuration.bootstrap.ConfigurationManagerBootstrapImpl.init(ConfigurationManagerBootstrapImpl.java:236)

at com.sap.engine.core.configuration.bootstrap.ConfigurationManagerBootstrapImpl.<init>(ConfigurationManagerBootstrapImpl.java:49)

at com.sap.engine.configtool.visual.ConfigTool.loadClusterData(ConfigTool.java:153)

at com.sap.engine.configtool.visual.ConfigTool.initScan(ConfigTool.java:135)

at com.sap.engine.configtool.visual.ConfigTool.<init>(ConfigTool.java:124)

at com.sap.engine.configtool.visual.ConfigTool.main(ConfigTool.java:1147)

at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)

at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:85)

at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:58)

at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:60)

at java.lang.reflect.Method.invoke(Method.java:391)

at com.sap.engine.offline.OfflineToolStart.main(OfflineToolStart.java:81)

Caused by: com.ibm.db2.jcc.b.SqlException: [ibm][db2][jcc][t4][2013][11249] Connection authorization failure occurred. Reason: User ID or Password invalid.

at com.ibm.db2.jcc.a.b.m(b.java:2006)

at com.ibm.db2.jcc.a.b.c(b.java:1659)

at com.ibm.db2.jcc.a.bb.r(bb.java:792)

at com.ibm.db2.jcc.a.bb.k(bb.java:349)

at com.ibm.db2.jcc.a.bb.c(bb.java:133)

at com.ibm.db2.jcc.a.b.yc(b.java:1283)

at com.ibm.db2.jcc.a.b.b(b.java:1204)

at com.ibm.db2.jcc.a.b.y(b.java:4593)

at com.ibm.db2.jcc.a.b.b(b.java:758)

at com.ibm.db2.jcc.a.b.a(b.java:701)

at com.ibm.db2.jcc.a.b.a(b.java:378)

at com.ibm.db2.jcc.a.b.<init>(b.java:316)

at com.ibm.db2.jcc.DB2Driver.connect(DB2Driver.java:166)

at com.sap.sql.jdbc.NativeConnectionFactory.createNativeConnection(NativeConnectionFactory.java:215)

at com.sap.sql.connect.OpenSQLDataSourceImpl.createPooledConnection(OpenSQLDataSourceImpl.java:608)

at com.sap.sql.connect.OpenSQLDataSourceImpl.getPooledConnection(OpenSQLDataSourceImpl.java:285)

at com.sap.engine.core.configuration.impl.persistence.rdbms.DBConnectionPool.createConnection(DBConnectionPool.java:307)

... 15 more

java.lang.reflect.InvocationTargetException

at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)

at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:85)

at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:58)

at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:60)

at java.lang.reflect.Method.invoke(Method.java:391)

at com.sap.engine.offline.OfflineToolStart.main(OfflineToolStart.java:81)

Caused by: java.lang.NullPointerException

at com.sap.engine.configtool.visual.ConfigTool.checkConfiguration(ConfigTool.java:183)

at com.sap.engine.configtool.visual.ConfigTool.loadClusterData(ConfigTool.java:173)

at com.sap.engine.configtool.visual.ConfigTool.initScan(ConfigTool.java:135)

at com.sap.engine.configtool.visual.ConfigTool.<init>(ConfigTool.java:124)

at com.sap.engine.configtool.visual.ConfigTool.main(ConfigTool.java:1147)

... 6 more

Its grateful for your suggestion.

Thanks

Edited by: kumar panu on Mar 28, 2011 1:27 PM

[Former Member · Accepted solution]

Hi Kumar,

I faced the similar issue to open the config tool, you have to replace the configtool directory as mentioned in the Sap oss notes 1513450 and 1408176, with the new configtool directory you will get Secstore tab to update the password.

Cheers,

Satyanarayana Devanabanda.

[Former Member · Accepted solution]

Hi Guys,

Issue resolved by implementing SAP Note 1513450.

Thanks

Kumar

[sunny_pahuja2]

Hi,

Change SAP<SID>DB password from OS level again to old value. After changing, you will be able to login to config tool and then again change the password from config tool.

Thanks

Sunny

[Former Member]

Hi Sunny,

But i dont know the previous password.

Regards

Kumar

[Former Member]

Hi Kumar,

Don't worry to forget the db password Now, you need to apply two major steps, below;

1) Configtool configuration entires are stored in "/usr/sap/<SID>/SYS/global/security/data/SecStore.properties" file, on Java stack. So, you can use "diagtool" in order to read encrypted secstore content. If you didn't change your entries in your secstore file, you can read old database password by using this tool. Check "Note 957666 - Diagtool for Troubleshooting Security Configuration" for details and download this tool.

2) After you get the db password, you should execute "sqlplus" and execute, SQL statement (Oracle), below;

alter user SAP<SID>DB identified by <old_password_read_by_diagtool>;

Or use brtools to change password which is my favourite

I hope that I clarified the issue.

Best regards,

Orkun Gedik

Senior SAP Netweaver and Development Consultant

SAP Technical Architect

Edited by: Orkun Gedik on Mar 28, 2011 4:39 PM

Edited by: Orkun Gedik on Mar 28, 2011 4:41 PM

[sunny_pahuja2]

Hi,

Open ConfigTool

- A pop-up will appear asking if you want to use the default DB settings

- Click on "Yes"

- You will receive an error message that you can't connect to the database

- Click on "Ok"

- In you left side, you will see "secure store". Click on it.

- Then in your right side, you will see the settings of database connection

- Change the password of user SAP<SID>DB in the parameter dbc/pool/<SID>/Password

- Apply the changes pressing the save button

- Restart the entire J2EE Engine

Thanks

Sunny

[Former Member]

Hi All,

Now, i am getting different error when i open configtool.sh as below...

com.sap.engine.frame.core.configuration.ConfigurationException: Error while connecting to DB.

at com.sap.engine.core.configuration.impl.persistence.rdbms.DBConnectionPool.createConnection(DBConnectionPool.java:365)

at com.sap.engine.core.configuration.impl.persistence.rdbms.DBConnectionPool.<init>(DBConnectionPool.java:130)

at com.sap.engine.core.configuration.impl.persistence.rdbms.PersistenceHandler.<init>(PersistenceHandler.java:38)

at com.sap.engine.core.configuration.impl.cache.ConfigurationCache.<init>(ConfigurationCache.java:149)

at com.sap.engine.core.configuration.bootstrap.ConfigurationManagerBootstrapImpl.init(ConfigurationManagerBootstrapImpl.java:236)

at com.sap.engine.core.configuration.bootstrap.ConfigurationManagerBootstrapImpl.<init>(ConfigurationManagerBootstrapImpl.java:49)

at com.sap.engine.configtool.visual.ConfigTool.loadClusterData(ConfigTool.java:153)

at com.sap.engine.configtool.visual.ConfigTool.initScan(ConfigTool.java:135)

at com.sap.engine.configtool.visual.ConfigTool.<init>(ConfigTool.java:124)

at com.sap.engine.configtool.visual.ConfigTool.main(ConfigTool.java:1147)

at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)

at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:85)

at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:58)

at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:60)

at java.lang.reflect.Method.invoke(Method.java:391)

at com.sap.engine.offline.OfflineToolStart.main(OfflineToolStart.java:81)

Caused by: com.ibm.db2.jcc.b.DisconnectException: [ibm][db2][jcc][t4][2043][11550] Exception java.net.ConnectException: Error opening socket to server GDPEXD:1X.XX.XX.XX on port 5,912 with message: A remote host refused an attempted connect operation..

at com.ibm.db2.jcc.a.xb.a(xb.java:380)

at com.ibm.db2.jcc.a.xb.<init>(xb.java:76)

at com.ibm.db2.jcc.a.a.x(a.java:265)

at com.ibm.db2.jcc.a.b.a(b.java:1785)

at com.ibm.db2.jcc.b.bb.a(bb.java:390)

at com.ibm.db2.jcc.b.bb.<init>(bb.java:350)

at com.ibm.db2.jcc.a.b.<init>(b.java:314)

at com.ibm.db2.jcc.DB2Driver.connect(DB2Driver.java:166)

at com.sap.sql.jdbc.NativeConnectionFactory.createNativeConnection(NativeConnectionFactory.java:215)

at com.sap.sql.connect.OpenSQLDataSourceImpl.createPooledConnection(OpenSQLDataSourceImpl.java:608)

at com.sap.sql.connect.OpenSQLDataSourceImpl.getPooledConnection(OpenSQLDataSourceImpl.java:285)

at com.sap.engine.core.configuration.impl.persistence.rdbms.DBConnectionPool.createConnection(DBConnectionPool.java:307)

... 15 more

Caused by: java.net.ConnectException: A remote host refused an attempted connect operation.

at java.net.PlainSocketImpl.socketConnect(Native Method)

at java.net.PlainSocketImpl.doConnect(PlainSocketImpl.java:355)

at java.net.PlainSocketImpl.connectToAddress(PlainSocketImpl.java:220)

at java.net.PlainSocketImpl.connect(PlainSocketImpl.java:207)

at java.net.Socket.connect(Socket.java:479)

at com.ibm.db2.jcc.a.y.run(y.java:34)

at java.security.AccessController.doPrivileged(AccessController.java:246)

at com.ibm.db2.jcc.a.xb.a(xb.java:374)

... 26 more

java.lang.reflect.InvocationTargetException

at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)

at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:85)

at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:58)

at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:60)

at java.lang.reflect.Method.invoke(Method.java:391)

at com.sap.engine.offline.OfflineToolStart.main(OfflineToolStart.java:81)

Caused by: java.lang.NullPointerException

at com.sap.engine.configtool.visual.ConfigTool.checkConfiguration(ConfigTool.java:183)

at com.sap.engine.configtool.visual.ConfigTool.loadClusterData(ConfigTool.java:173)

at com.sap.engine.configtool.visual.ConfigTool.initScan(ConfigTool.java:135)

at com.sap.engine.configtool.visual.ConfigTool.<init>(ConfigTool.java:124)

at com.sap.engine.configtool.visual.ConfigTool.main(ConfigTool.java:1147)

[Former Member]

Hi Sunny,

Open ConfigTool

- A pop-up will appear asking if you want to use the default DB settings

- Click on "Yes"

- You will receive an error message that you can't connect to the database

- Click on "Ok"

After this i am unable to see pop screen its gets closed.

please see above error....

Regards,

Kumar

[Former Member]

Hi Kumar,

Do you have this error regarding my recommendation?

Best regards,

Orkun Gedik

[Former Member]

Hi Orkun Gedik,

Before ur recommendation i simply changed SAP<SID>DB Password by smitty tool and maintained same password db2<SID> and SAP<SID>DB.

Successfully login to user SAP<SID>DB.

Afterwards i tried to connect to server through configtool.sh but failed.

Please find above is the error...

Regards,

Kumar

[Former Member]

HI sunny pahuja

                          I am getting the same above error while opening  the config tool.below i  mentioned  the  error details for jcontrol.exe is not starting in java stack. i had followed  the note  for 1513450.Kindly revert the posotive  reply

   ,when  i  execute the below commands.

<logon as <sid>adm>

  dscdb6up <sid>adm <password>

  dscdb6up sap<sid> <password>

after execute the following above command,result of the error.

error:unable to open  file:'\\erpprn\sapmnt\ERG\SYS\global\dscdb6.conf".

2.db2 START  command log below I mentioned:

------------------------------ Commands Entered ------------------------------

db2start;

------------------------------------------------------------------------------

db2start

SQL1026N  The database manager is already active.

SQL1026N  The database manager is already active.

Explanation:

A start database manager command is already processed. 

The command cannot be processed. 

User Response:

Because the command is already processed, the application may

continue processing. 

A JDBC connection to the target has succeeded.

Kindly need your positive quick reply.

Thanks