DB13 /CONNECT invalid username/password; logon denied

[former_member266763]

Dear All,

After system upgrade to EHP7 on oracle 12c . DB 13 failed Genet-rating error . unable to take backup. please guide

Job started
Step 001 started (program RSDBAJOB, variant &0000000000260, user ID BASIS)
Execute logical command BRBACKUP On host NFLDEV
Parameters:-jid ALL__20161004164951 -u / -c force -t online -m all -p initR3D.sap
BR0051I BRBACKUP 7.40 (24)
BR0055I Start of database backup: beufajhv.ant 2016-10-04 16:49:51
BR0484I BRBACKUP log file: /oracle/R3D/sapbackup/beufajhv.ant
BR0280I BRBACKUP time stamp: 2016-10-04 16:49:52
BR0301E SQL error -1017 at location BrDbConnect-3, SQL statement:
'CONNECT /'
ORA-01017: invalid username/password; logon denied
BR0310E Connect to database instance R3D failed


BR0056I End of database backup: beufajhv.ant 2016-10-04 16:49:52
BR0280I BRBACKUP time stamp: 2016-10-04 16:49:52
BR0054I BRBACKUP terminated with errors
External program terminated with exit code 3
BRBACKUP returned error status E
Job finished

S

QL> SELECT OWNER, TABLE_OWNER, TABLE_NAME FROM DBA_SYNONYMS WHERE SYNONYM_NAME = 'SAPUSER';


no rows selected


SQL> desc SAPUSER;
ERROR:
ORA-04043: object SAPUSER does not exist

orar3d 53> sqlplus /
SQL*Plus: Release 12.1.0.2.0 Production on Tue Oct 4 16:54:38 2016
Copyright (c) 1982, 2014, Oracle.  All rights reserved.
ERROR:
ORA-01017: invalid username/password; logon denied

[JamesZ]

Hi Imran,

This means <sid>adm ops$ user is not working, we can reproduce this issue as followings:

log on db server via user <sid>adm
sqlplus /nolog
conn /

Please configure ops$ user for <sid>adm user.

Best regards,
James

[Reagan]

>>SQL> desc SAPUSER;<<

You should specify the table owner before the table name (assuming that you are not connected under that user). Eg: ops$r3dadm.sapuser;

Apart from that, you have Oracle release 12 and the SAP kernel release is 740. So your system should be set up with SSFS. In that case the table SAPUSER is no longer valid or present as part of the SSFS set up you drop the SAPUSER table also. The table SAPUSER is for OPS$ mechanism which is no longer used. This is the reason why you are getting the ORA-01017 error when you connect using / (OPS$) and also the DB13 is still using / (OPS$) for backups. The DB13 job was executed from SAP so the SAP system is up and running. That means you don't need to worry about the ABAP and DB connectivity. The problem is with the backup not using the correct authentication mechnism to connect to the database to take the backup.

Check note 1764043 - Support for secure storage in BR*Tools and the attached scripts to modify the SDBAC table.

[Former Member]

Hi Reagan Benjamin,

we are setup SSFS according to the note 1764043 - Support for secure storage in BR*Tools

3. Storage of BR*Tools user/password in secure storage

rsecssfx changekey <ext_key>

How we maintain this key

:r3dadm 52> rsecssfx changekey 0123456789ABCDEF

SSFS-5192: The key value has an incorrect syntax (reason: Key compound

has incorrect length for key of type 1). When you are in the process of

changing the encryption key, use command "rsecssfx generatekey" to

generate a valid random encryption key.

Regards

Imran

[Reagan]

Just follow this article.

[Former Member]

I am Facing

orar3d 57> brconnect -u // -c -f check

BR0801I BRCONNECT 7.40 (24)

BR0805I Start of BRCONNECT processing: ceufjgii.chk 2016-10-06 12:12:40

BR0484I BRCONNECT log file: /oracle/R3D/sapcheck/ceufjgii.chk

BR0477I Oracle pfile /oracle/R3D/sapprof/initR3D.ora created from spfile /oracle                                                                                        /R3D/121/dbs/spfileR3D.ora

BR1805I Oracle spfile /oracle/R3D/sapprof/spfileR3D.ora created from pfile /orac                                                                                        le/R3D/sapprof/initR3D.ora

BR0280I BRCONNECT time stamp: 2016-10-06 12:12:42

BR0813I Schema owners found in database R3D:

ANONYMOUS, APPQOSSYS, AUDSYS, BRT$ADM, DBSNMP, DIP, GSMADMIN_INTERNAL, GSMCATUSE                                                                                        R, GSMUSER, OPS$ORACLE,

OPS$R3DADM, OPS$SAPSERVICER3D, ORACLE_OCM, OUTLN, SAPSR3*, SYS, SYSBACKUP, SYSDG                                                                                        , SYSKM, SYSTEM,

XDB

BR0280I BRCONNECT time stamp: 2016-10-06 12:12:48

BR0814I Number of tables/partitions in schema of owner SAPSR3: 96237/10

BR0836I Number of tables treated as info cubes for owner SAPSR3: 515

BR0814I Number of tables/partitions in schema of owner SYS: 1157/478

BR0814I Number of tables/partitions in schema of owner SYSTEM: 171/46

BR0280I BRCONNECT time stamp: 2016-10-06 12:12:57

BR0815I Number of indexes/partitions in schema of owner SAPSR3: 116147/51

BR0815I Number of indexes/partitions in schema of owner SYS: 1180/333

BR0815I Number of indexes/partitions in schema of owner SYSTEM: 233/68

BR0280I BRCONNECT time stamp: 2016-10-06 12:13:10

BR0816I Number of segments in schema of owner DBSNMP: 8

BR0816I Number of segments in schema of owner GSMADMIN_INTERNAL: 20

BR0816I Number of segments in schema of owner OUTLN: 9

BR0816I Number of segments/LOBs in schema of owner SAPSR3: 65911/4327

BR0816I Number of segments/LOBs in schema of owner SYS: 3532/174

BR0816I Number of segments/LOBs in schema of owner SYSTEM: 448/22

BR0816I Number of segments in schema of owner XDB: 704

BR0280I BRCONNECT time stamp: 2016-10-06 12:13:10

BR0961I Number of conditions found in DBCHECKORA: 128

BR0280I BRCONNECT time stamp: 2016-10-06 12:13:10

BR0301E SQL error -1031 at location BrDbdiffRead-1, SQL statement:

'PREPARE stmt_5 FROM'

'SELECT OBJNAME FROM "SAPSR3".DBDIFF WHERE DBSYS IN ('ORACLE', ' ') AND OBJTYPE = 'TABL' AND DIFFKIND IN ('02', '61', '99') ORDER BY OBJNAME'

ORA-01031: insufficient privileges

BR0806I End of BRCONNECT processing: ceufjgii.chk 2016-10-06 12:13:10

BR0280I BRCONNECT time stamp: 2016-10-06 12:13:10

BR0804I BRCONNECT terminated with errors

Please Guide.

Khan

[kaus19d]

, Did you before commenting again & posting again the same post in here, did you at least try what me & our friends suggested? Do you even understand your system & those suggestions that we are providing?? Or you are simply posting reply or maybe you are looking for a direct person who can come to your office to do your job? If that is the case, then, its not going to happen as because we are not your employees. Just because you are getting the suggestions free of cost here, it does not mean that we will go there at your place to do the job or take remote & do the job, the suggestions what you are getting, those are valuable & that is why you implement those solutions & then only post. If you are totally like, yesterday born person, then I guess you should take up some training & then go for the job.

For example, here its saying insufficient privilege for dB tables in BRTOOLS, so did you try using ORA<SID> or <SID>adm login. Run check for R3trans -d -w & check login for sqlplus '/as sysdba'

sql> alter database default tablespace users

Also check out the below(you should have searched before posting, because we will not do hand-feeding you for every single matter of your issue), so did you check the below links before commenting here?

BRBACKUP: ORA-01031: insufficient privileges | SCN

Oracle BRtools Backup issue | SCN

Problem in BRTOOLS | SCN

Thanks,

Kaushik

[Former Member]

This error resolved

1.login as orasid

2.sqlplus "/as sysdba"

3.

grant ALL on SAPSR3.SDBAH to sapdba;

grant ALL on SAPSR3.SDBAD to sapdba;

grant ALL on SAPSR3.DBAML to sapdba;

grant ALL on SAPSR3.DBARCL to sapdba;

grant ALL on SAPSR3.DBAFID to sapdba;

grant ALL on SAPSR3.DBAEXTL to sapdba;

grant ALL on SAPSR3.DBAREOL to sapdba;

grant ALL on SAPSR3.DBABARL to sapdba;

grant ALL on SAPSR3.DBADFL to sapdba;

grant ALL on SAPSR3.DBAOPTL to sapdba;

grant ALL on SAPSR3.DBASPAL to sapdba;

grant ALL on SAPSR3.DBABD to sapdba;

grant ALL on SAPSR3.DBABL to sapdba;

grant ALL on SAPSR3.DBATL to sapdba;

grant ALL on SAPSR3.DBAOBJL to sapdba;

grant ALL on SAPSR3.DBAPHAL to sapdba;

grant ALL on SAPSR3.DBAGRP to sapdba;

grant ALL on SAPSR3.DBAERR to sapdba;

grant ALL on SAPSR3.DBATRIAL to sapdba;

grant ALL on SAPSR3.DBSTATC to sapdba;

grant ALL on SAPSR3.DBSTATTORA to sapdba;

grant ALL on SAPSR3.DBSTATIORA to sapdba;

grant ALL on SAPSR3.DBSTATHORA to sapdba;

grant ALL on SAPSR3.DBSTAIHORA to sapdba;

grant ALL on SAPSR3.DBMSGORA to sapdba;

grant ALL on SAPSR3.DBCHECKORA to sapdba;

grant ALL on SAPSR3.MLICHECK to sapdba;

grant SELECT on SAPSR3.TGORA to sapdba;

grant SELECT on SAPSR3.IGORA to sapdba;

grant SELECT on SAPSR3.TSORA to sapdba;

grant SELECT on SAPSR3.TAORA to sapdba;

grant SELECT on SAPSR3.IAORA to sapdba;

grant SELECT on SAPSR3.SVERS to sapdba;

grant SELECT on SAPSR3.CVERS to sapdba;

grant SELECT on SAPSR3.DD02L to sapdba;

grant SELECT on SAPSR3.DD09L to sapdba;

grant SELECT on SAPSR3.DDNTT to sapdba;

grant SELECT on SAPSR3.DDART to sapdba;

grant SELECT on SAPSR3.DARTT to sapdba;

grant SELECT on SAPSR3.DBCHK to sapdba;

grant SELECT on SAPSR3.DBDIFF to sapdba;

grant ALL on SAPSR3.SAPLIKEY to sapdba;

grant SELECT on SAPSR3.RSNSPACE to sapdba;

grant SELECT on SAPSR3.RSPSPACE to sapdba;

Regards

Khan

[Former Member]

Hi Kaushik,

I am very much surprise your language. Behave like a good teacher.  Mr. Reagan Benjamin give me excellent help, that 's why i am very much near to solution.

Currently i am facing some space issue at server.

Khan

[kaus19d]

Hi,

check whether you are able to open the BRTOOLS or you are able to run SQLPLUS '/AS SYSDBA' or the SHOWSGA command. If BRTOOLS opening, then 1st check whether able to run through BRTOOLS Backup program directly.

Thanks,

Kaushik

[Former Member]

Hi

Please go through below sap notes

https://launchpad.support.sap.com/#/notes/1576837/E

https://launchpad.support.sap.com/#/notes/776505/E

Check if R3trans -d reports any error in trans.log file.

Also check if Br*tools files have proper permissions..

Set the SGID bit for the brarchive, brbackup, and brconnect executables (they must belong to ora<dbsid>):

cd /usr/sap/<SAPSID>/SYS/exe/run

chown ora<dbsid> brarchive brbackup brconnect

chgrp dba brarchive brbackup brconnect

chmod 6754 brarchive brbackup brconnect

These commands should result in the following file authorizations:

-rwsr-sr-- 1 ora<dbsid>  dba     9325374 2012-12-19 04:52 brarchive

-rwsr-sr-- 1 ora<dbsid>  dba     9443223 2012-12-19 04:52 brbackup

-rwsr-sr-- 1 ora<dbsid>  dba    11333756 2012-12-19 04:55 brconnect

-rwxr-xr-x 1 <sapsid>adm sapsys  9893702 2012-12-19 04:56 brrecover

-rwxr-xr-x 1 <sapsid>adm sapsys  6203096 2012-12-19 04:56 brrestore

-rwxr-xr-x 1 <sapsid>adm sapsys 11766827 2012-12-19 04:58 brspace

-rwxr-xr-x 1 <sapsid>adm sapsys  6797524 2012-12-19 04:58 brtools

Regards

Prithviraj