cancel
Showing results for 
Search instead for 
Did you mean: 

ora-01017 after change system password

Former Member
0 Kudos

Dear all,

i attempt this error during the brbackup, after the change of system password on oracle

"ora-01017 invalid username password logon denied

system/*********"

Infact, if i restore the default password (manager) the brbackup works fine.

The question is: could be sufficient change the password on brtools?

brconnect -f chpass -o system -p <new_password>

or i have to drop and recreate the OPS$ too?

DELETE FROM "OPS$<sid>ADM".SAPUSER;

INSERT INTO "OPS$<sid>ADM".SAPUSER VALUES ('<sapowner>', '<password>');

But the OPS$ mechanism works, because the sqlplus /@SID works!

the ossnote

Note 562863 - FAQ: Logon mechanisms

SYSTEM: By default, sapdba and the BR tools are connected to the database with the SYSTEM user and standard password. If you change this now, you can only start the tools by explicitly specifying the user name and password. To do this, use the option "-u <username>/<password>". Otherwise, calling sapdba, brbackup, brconnect, brarchive and brrestore fails with ORA-01017.

A useful alternative to the SYSTEM user when using the BR*TOOLS is to use the OPS$ mechanism by specifying "-u/". This mechanism is also used by DB13 actions by default.

so, there is not solution if i change the default password of SYSTEM user????

i have to run the brbackup with a crontab script, so i CANNOT use the workaround "brbackup -u system/newpassword" because i cannot leave this password clear on a file, but i must use the option "brbackup -u /"

Any idea?

tks!

Accepted Solutions (1)

Accepted Solutions (1)

Former Member
0 Kudos

In case of crontab script, we used to explicitly specify the updated password for the system user (clear on a file) whereas DB13 uses "brbackup -u /"

Thanks

Former Member
0 Kudos

if i put the OLD password (manager), the option -u / works on the crontab.

The problem is with the NEW password, because the -u / doesn't works, infact i have to put -u system/newpassword.

Former Member
0 Kudos

if i put the OLD password (manager), the option -u / works on the crontab.

The problem is with the NEW password, because the -u / doesn't works, infact i have to put -u system/newpassword.

Former Member
0 Kudos

There must be something wrong, either with the configuration of OPS$ user, or with your crontab entry.

Please double check!

The note you quoted above clearly says that either -u / or system will be used, but not both.

regards

Former Member
0 Kudos

SOLVED!

the problem is the group DBA (no present on orasid) !!!!

now, the -u / works fine

ciao!

Answers (1)

Answers (1)

Former Member
0 Kudos

Hi,

>> The question is: could be sufficient change the password on brtools?

brconnect -f chpass -o system -p <new_password>

It is good enough to change the password. It will create the entry on SAPUSER table,

>> or i have to drop and recreate the OPS$ too?

No, you don't need this.

You can use brbackup -u / without any problem. What makes trouble with it?

Best regards,

Orkun Gedik