4EETQ399 1 [ dbsloci.c,13255]: SAPUSER error or connect error 99=DBSL_ERR_DB, oerr=12518.

1 ETQ000 ==================================================
1 ETQ399 Executing SQL script '..\var\SQLDBSCRIPT.TQL'.
2 ETQ399 Connecting to database 'ora'.
3EETQ008 Error message: DBSL error 99 (db code -1): Connect failed
4EETQ399 1 [ dbsloci.c,13221]: Logon as OPS$-user to get SAPSR3's password
4EETQ399 1 [ dbsloci.c,16053]: Connecting as /@SOL
on connection 0 (nls 0) ... (dbsl 721 030315, UNICODE[2])
4EETQ399 1 [   dboci.c, 4491]: OCIHandleAlloc(con=0): Service svc=0B357960 created, rc=0
4EETQ399 1 [   dboci.c, 4154]:    OCIServerAttach(OCI_DEFAULT) failed with SQL error 12518:
4EETQ399 1 [   dboci.c, 4157]:    ORA-12518: TNS:listener could not hand off client connection                                                                 
4EETQ399 1 [   dboci.c, 4666]: OCIServerAttach(con=0, svc=0B357960): Error 12518 attaching new srv=0B357B40 to 'SOL'
4EETQ399 1 [   dboci.c, 4669]: OCIHandleFree(con=0): Server handle srv=0B357B40 freed.
4EETQ399 1 [   dboci.c, 4507]: OCIHandleFree(con=0): Service svc=0B357960 freed (i=0).
4EETQ399 1 [   dboci.c, 4511]: rc=12518 -> Trying to reattach to server 'SOL'
4EETQ399 1 [   dboci.c, 4491]: OCIHandleAlloc(con=0): Service svc=0B357960 created, rc=0
4EETQ399 1 [   dboci.c, 4154]:    OCIServerAttach(OCI_DEFAULT) failed with SQL error 12518:
4EETQ399 1 [   dboci.c, 4157]:    ORA-12518: TNS:listener could not hand off client connection                                                                 
4EETQ399 1 [   dboci.c, 4666]: OCIServerAttach(con=0, svc=0B357960): Error 12518 attaching new srv=0B357B40 to 'SOL'
4EETQ399 1 [   dboci.c, 4669]: OCIHandleFree(con=0): Server handle srv=0B357B40 freed.
4EETQ399 1 [   dboci.c, 4507]: OCIHandleFree(con=0): Service svc=0B357960 freed (i=1).
4EETQ399 0 [ dbsloci.c,16069]: CONNECT failed with SQL error '12518'
4EETQ399 1 [ dbsloci.c,13255]: SAPUSER error or connect error 99=DBSL_ERR_DB, oerr=12518.


Solution:

Wrong password combination of OPS$sapserviceSID in database and OPS$sapserviceSID on Oslevel,
make both password is same.,
 

BR0301E SQL error -942 at location db_connect-6, SQL statement:'SELECT NAME FROM V$DATABASE WHERE ROWNUM = 1'ORA-00942: table or view does not exist

Error after Upgrade or System copy:

C:\Users\gpdadm>brconnect -u / -c -f stats -t all -f collect -p 4
BR0801I BRCONNECT 7.20 (36)
BR0805I Start of BRCONNECT processing: ceqyckdt.sta 2015-07-13 12.02.33
BR0484I BRCONNECT log file: E:\oracle\GPD\sapcheck\ceqyckdt.sta
BR0280I BRCONNECT time stamp: 2015-07-13 12.02.34
BR0301E SQL error -942 at location db_connect-6, SQL statement:
'SELECT NAME FROM V$DATABASE WHERE ROWNUM = 1'
ORA-00942: table or view does not exist
BR0310E Connect to database instance GPD failed
BR0280I BRCONNECT time stamp: 2015-07-13 12.02.34
BR0301W SQL error -942 at location brc_dblog_open-1, SQL statement:
'INSERT INTO SAP_SDBAH (BEG, FUNCT, SYSID, OBJ, RC, ENDE, ACTID, LINE) VALUES ('
20150713120233', 'sta', 'GPD', 'ALL', '9999', ' ', 'ceqyckdt', '7.20 (36)')'
ORA-00942: table or view does not exist
BR0324W Insertion of database log header failed
BR0806I End of BRCONNECT processing: ceqyckdt.sta 2015-07-13 12.02.34
BR0280I BRCONNECT time stamp: 2015-07-13 12.02.34
BR0804I BRCONNECT terminated with errors

Solution:

Solution:

SQL> grant sapconn, unlimited tablespace to PSAPSR3
  2  ;
grant sapconn, unlimited tablespace to PSAPSR3
                                       *
ERROR at line 1:
ORA-01917: user or role 'PSAPSR3' does not exist

SQL> grant sapconn, unlimited tablespace to SAPSR3;
Grant succeeded.
SQL> COMMIT;
Commit complete.
SQL> grant sYSTEM, unlimited tablespace to SAPSR3;
grant sYSTEM, unlimited tablespace to SAPSR3
      *
ERROR at line 1:
ORA-01919: role 'SYSTEM' does not exist

SQL> grant sysdba, unlimited tablespace to SAPSR3;
Grant succeeded.
SQL> commit;
Commit complete.
SQL>



SQL> grant sysoper to sapsr3;
Grant succeeded.
SQL> grant sapconn to sapsr3
  2  ;
Grant succeeded.
SQL> grant sapdba to sapsr3;
Grant succeeded.
SQL> alter user SAPSR3 default role all;
User altered.
SQL> select grantee, granted_role, default_role
  2        from dba_role_privs
  3         where grantee = 'SAPSR3';
GRANTEE                        GRANTED_ROLE                   DEF
------------------------------ ------------------------------ ---
SAPSR3                         SAPCONN                        YES
SAPSR3                         SAPDBA                         YES
SQL> select * from session_roles;
no rows selected
SQL>

 ====================================================================
D:\usr\sap\GPD\SYS\exe\NTAMD64>sqlplus /nolog @sapdba_role  SR3
SQL*Plus: Release 11.2.0.3.0 Production on Thu Apr 23 19:29:19 2015
Copyright (c) 1982, 2011, Oracle.  All rights reserved.
Disconnected from Oracle Database 11g Enterprise Edition Release 11.2.0.3.0 - 64
bit Production
With the Partitioning, OLAP, Data Mining and Real Application Testing option
D:\usr\sap\GPD\SYS\exe\NTAMD64> sqlplus /nolog @sapdba_role SAPSR3

sqlplus /nolog @sapconn_role.sql SR3
sqlplus /nolog @sapconn_role.sql SAPSR3

Symptom If database accesses are performed using the database tools BRBACKUP, BRARCHIVE, BRCONNECT, and BRSPACE, the relevant authorizations are missing. BRBACKUP fails with the following error messages, for example: BR0051I BRBACKUP 7.00 (20) BR0055I Start of database backup: bddzbuxf.ant 2009-11-10 10.12.35 BR0280I Time stamp 2009-11-10 10.12.36 BR0301W SQL error -1031 at location BrLicCheck-7 ORA-01031: insufficient privileges BR0301W SQL error -942 at location BrbDbLogOpen-1 ORA-00942: table or view does not exist BR0324W Insertion of database log header failed BR0280I Time stamp 2009-11-10 10.12.37 BR0301E SQL error -1031 at location BrCntrlCopy-1 ORA-01031: insufficient privileges BR0320E Copying of control file to ... failed BR0314E Collection of information on database files failed BR0056I End of database backup: bddzbuxf.ant 2009-11-10 10.12.37 BR0280I Time stamp 2009-11-10 10.12.37 BR0054I BRBACKUP terminated with errors In relation to table functions, the following errors, for example, can occur in SAP Release 7.40 SP10 or above: BR0301E SQL error -1031 at location stats_tfun_update-2, SQL statement: 'BEGIN SAP091.UCONRFC_ATTRG (0, 1); END;' ORA-01031: insufficient privileges ORA-06512: at "SAP091.UCONRFC_ATTRG", line 1 ORA-06512: at line 1 BR1867E Updating statistics failed for table function SAP091.UCONRFC_ATTR Other Terms SAPDBA role, BR*Tools Reason and Prerequisites 1. You did not create the SAPDBA role during an SAP/Oracle upgrade, as outlined in the upgrade instructions. 2. You use one of the tools mentioned above in a lower SAP release and the database authorizations have not been adjusted. 3. The database grants were deleted. Solution Download the SQL script for creating the SAPDBA role from the attachment to this SAP Note (for Oracle 10g: sapdba_role_ora10, for Oracle 11g: sapdba_role_ora11, and for Oracle 12c: sapdba_role_ora12 ). Execute this script as follows (sapdba_role.sql in the current directory): sqlplus /nolog @sapdba_role <SAPSCHEMA_ID> Where <SAPSCHEMA_ID> is the schema ID of the SAP database user: - for User SAPR3:      R3 - For the user SAPSR3:     SR3 - for User SAP<SID>:   <SID> - for User SAP<SID>DB: <SID>DB Sample call for a standard installation with the schema SAPSR3: sqlplus /nolog @sapdba_role SR3 and with the schema SAPR3: sqlplus /nolog @sapdba_role R3 The log file sapdba_role.log is created in the current directory. Note 1: ---------- The schema ID is not to be confused with the schema name. Therefore, the following call is incorrect: sqlplus /nolog @sapdba_role SAPSR3 Caution 2 ---------- For MCOD systems, the script must be executed for all SAP schemas, for example, for ABAP schemas and Java schemas in a database: sqlplus /nolog @sapdba_role SR3 sqlplus /nolog @sapdba_role SR3DB Caution 3 ---------- Since non-ABAP systems/schemas (a pure SAP J2EE database, for example) do not contain all of the tables mentioned in the SAPDBA role, the log file will contain error messages, for example: grant ALL on SAPSR3DB.DBAML to sapdba                       * ERROR at line 1: ORA-00942: table or view does not exist You can ignore these error messages.

Thanks
Yoonus

1173159 - BR*Tools errors occur when accessing "database" directory

Symptom

The following errors occur in Oracle 10g or higher:

Symptom 1
---------
When you access the directory %ORACLE_HOME%\database, the system displays the following warnings of BR*Tools on Windows platforms, for example:
BR0252W Function remove() failed for 'D:\oracle\SID\102\database\sapSID.ora' at location BrInitOraCreate-1
BR0253W errno 13: Permission denied
BR0252W Function remove() failed for 'D:\oracle\SID\102\database\sapSID.ora' at location BrInitOraCopy-7
BR0253W errno 13: Permission denied

Symptom 2
---------
After you use the Database Upgrade Assistant (DBUA) to apply Oracle patch set 10.2.0.4, BRBACKUP and BRCONNECT fail and the system issues error messages such as:
BR0252E Function CreateFile() failed for 'E:\oracle\SID\102\database\spfileSID.ora' at location BrFileStatGet-2
BR0253E errno 5: Access is denied.
BR0273E Determination of file status for E:\oracle\SID\102\database\spfileSID.ora failed

Other Terms

BR*Tools, BRBACKUP, BRCONNECT

Reason and Prerequisites

1173159 - BR*Tools errors occur when accessing "database" directory

These problems occur only if you use the SAP system (transaction DB13) to start BRBACKUP or BRCONNECT.
Symptom 1 occurs if the Oracle software was not installed in an SAPinst operation in which the access authorizations are automatically adjusted to the database directory.
Symptom 2 does not occur if you applied patch set 10.2.0.4 manually (not using DBUA).

Solution

For symptom 1:
Under user <SID>ADM in a command prompt window, change the access authorizations on the database directory using the following commands:
cacls %ORACLE_HOME%\database /E /G ORA_OPER:F
cacls %ORACLE_HOME%\database /E /G ORA_%ORACLE_SID%_OPER:F
cacls %ORACLE_HOME%\database /E /G ORA_DBA:F
cacls %ORACLE_HOME%\database /E /G ORA_%ORACLE_SID%_DBA:F
For symptom 2:
To eliminate symptom 2, you must change the access authorizations so that they do not apply only to the database directory, but to all database files and the spfile. To avoid a large amount of manual steps, in BRCONNECT 7.00 Patch 39 and BRCONNECT 7.10 Patch 19, the workaround option "-SFP" (set file permissions) is provided for the "check" function. You can use this to perform a BRCONNECT call under the user <SID>ADM to set all of the required access authorizations, for example:
brconnect -u / -c -f check -SFP
In the process, the access authorizations to the following directories and the subdirectories and files under them are modified:
%ORACLE_HOME%\database,
<X>:\oracle\<DBDID>\origlog
<X>:\oracle\<DBDID>\mirrlog
<X>:\oracle\<DBDID>\sapdata<N>
If the system issues any warnings about Windows groups that do not exist (for example, ora_oper), you can ignore these.

Long long run MAIN_SHDRUN/ACT_UPG with all component Update

1387739 - Out of memory errors during shadow system operation

 

 

Long long run MAIN_SHDRUN/ACT_UPG with all component Update  sum,ehp ETC

 

 

Symptom

Out of memory error in ACT_UPG phase during EHP installation using SUM.
Dump EXSQL_DSQL_NOROLL in RUN_RADCUCNT_ALL SUM phase.

Other Terms

SUM ACT_UPG RDDMASGL TSV_TNEW_PAGE_ALLOC_FAILED SYSTEM_NO_ROLL TSV_LIN_ALLOC_FAILED RUN_RADCUCNT_ALL EXSQL_DSQL_NOROLL TSV_TNEW_OCCURS_NO_ROLL_MEMORY

Reason and Prerequisites

Mass-Activation program of the ABAP dictionary can run out of memory depending of the kind and number of packages included in the EHP installation.

Solution

Generally the solution is to change the memory parameters of the shadow system so that the dictionary activation program can use more physical memory.

Explanation of some terms used below:

• DIR_PUT can be found using the transaction AL11.

• Depending on the version of the update tool you are using following substitutions might be required:

           SUM -> SAPEHPI
           SAPup -> SAPehpi

Changing memory parameters of the shadow system

The relevant profile parameters of the shadow system and their values recommended for fixing the problem are:

abap/heap_area_total = 10000000000
abap/heap_area_nondia = 10000000000
ztta/roll_area = 20000000

To change the parameter you need to process as follows:

1. Stop the shadow system.

2. Add/change the mentioned parameters in the instance profile of the shadow  system. To find out the right file name and path of the shadow instance profile look in the log file <DIR_PUT>/log/SAPup.log for

              # SHD PROFILE PATH
              # SHD PROFILE NAME

3. Start shadow system.

4. Repeat the ACT phase.

Before changing this parameters make sure you have read the general memory notes 146289, 88416 (MS Windows), 941735 (64-bit Linux).
Preventive setting of the parameters
In some cases you might expect the described error to arise: for example, if the error already occurred during SUM execution on the test or development system and you are now about to update your productive system using the same EHP and SP stack.
If you are absolutely sure that the described error will arise in your planed SUM application you can set the memory parameters for the shadow system preventively in the phase START_SHDI_FIRST:

1. Execute the command

              <DIR_PUT> /bin/SAPup stop START_SHDI_FIRST
              You should execute this command after the update was started but before the phase START_SHDI_FIRST was processed.

2. When the EHPI/SUM stops in START_SHDI_FIRST change the profile parameters as described in the previous section.

              You don't need to start/stop shadow system!

3. Continue with the SUM.

It is not recommended to change the memory parameters of the shadow system in advance as described here if you are not sure that the error will occur! The changed settings may significantly reduce the performance of your productive system during the preprocessing phase of the SUM execution.

SAPup broke during phase SHDINST_OS in module PREP_INSTALL / Installation

This trouble ticket was created by SAPup on 20150711204813
-------------------------------------------------------------
SAPup broke during phase SHDINST_OS in module PREP_INSTALL / Installation
Error Message: Action 'install' for DCOM service failed, see phase log for details: Cannot create a file when that file already exists.

-------------------------------------------------------------
-------------------------------------------------------------
Summary of SAPup:
-------------------------------------------------------------
SAPehpi Release: lmt_004
SAPehpi Version: SAPup release lmt_004 version 58.000
Start Release:  701
Target Release:  702
-------------------------------------------------------------
Summary of host system details:
-------------------------------------------------------------
SID:   SOL
Host:   dummy-SolMan
MS Host:  dummy-SolMan
GW Host:  dummy-SolMan
Start Path:  C:\usr\sap\SOL\DVEBMGS00\exe
Kernel Path:  C:\usr\sap\SOL\DVEBMGS00\exe
-------------------------------------------------------------
Summary of operating system details:
-------------------------------------------------------------
OS Type:  Windows NT X86_64
OS Version:  6.0
-------------------------------------------------------------
Summary of database details:
-------------------------------------------------------------
Database Type:  ora
Database Version: 11.2.0.3.0
-------------------------------------------------------------
Summary of RFC details:
-------------------------------------------------------------
Host:   dummy-SolMan
GW Host:  dummy-SolMan
Client:   000
Destination:  SOL
Language:  E
System No.:  00
-------------------------------------------------------------
-------------------------------------------------------------



Solution:

This is caused due to incorrect SAPService<SID> user password provided to SUM.

 

Check your SAPService<SID> user password that you provided to SUM.

You might have provided incorrect password to SUM during the Configuration phase.

 

Change the SAPService<SID> user password to what you had provided to SUM.

Also make sure you update the same password in 'Services' related to instance owned by SAPService<SID> user.

 

Once done, resume your SUM, the error will no longer occur.

 

Thanks

Yoonus

 

Cannot construct a support package stack from file C:\usr\sap\trans\EPS\in\SMSDXML_SOL_20150710102541.516.xml. The stack is rejected because there were found kernels with different versions and/or make variants in the stack: 7.21 / and: 7.21EXT / EXT .

Cannot construct a support package stack from file C:\usr\sap\trans\EPS\in\SMSDXML_SOL_20150710102541.516.xml. The stack is rejected because there were found kernels with different versions and/or make variants in the stack: 7.21 / and: 7.21EXT / EXT .

Solution:_

To avoid these errors avoid selecting multiple kernel from the initial stage of xml stack file creation:

Thanks
Yoonus

OPS$ user ID creation after Backup restore to hetrogeniouse environment!!!

You just  modify according to your current system setup.

1.	Login to orasid and  execute  sqlplus "/as sysdba"

2.	CREATE USER "OPS$<Hostname>\<SID>ADM" DEFAULT TABLESPACE PSAPSR3 TEMPORARY TABLESPACE PSAPTEMP IDENTIFIED EXTERNALLY;

3.	SELECT GRANTED_ROLE FROM DBA_ROLE_PRIVS WHERE GRANTEE = 'OPS$<Hostname>\<SID>ADM';

4.	GRANT CONNECT, RESOURCE TO "OPS$<Hostname>\<SID>ADM";

5.	CREATE USER "OPS$<Hostname>\SAPSERVICE<SID>" DEFAULT TABLESPACE PSAPSR3USR TEMPORARY TABLESPACE PSAPTEMP IDENTIFIED EXTERNALLY;

6.	SELECT GRANTED_ROLE FROM DBA_ROLE_PRIVS WHERE GRANTEE = 'OPS$<Hostname>\SAPSERVICE<SID>';

7.	GRANT CONNECT, RESOURCE TO "OPS$<Hostname>\SAPSERVICE<SID>";

8.	SELECT OWNER FROM DBA_TABLES WHERE TABLE_NAME = 'SAPUSER';

9.	CREATE TABLE "OPS$<Hostname>\<SID>ADM".SAPUSER (USERID VARCHAR2(256), PASSWD VARCHAR2(256));

10.	INSERT INTO "OPS$<Hostname>\<SID>ADM".SAPUSER VALUES ('SAPSR3', 'Password');  sapuser schema name and  DBpassword ('OWNER', 'PASSWORD');

11.	SELECT OWNER, TABLE_OWNER, TABLE_NAME FROM DBA_SYNONYMS WHERE SYNONYM_NAME = 'SAPUSER'; SQL> SELECT OWNER FROM DBA_TABLES WHERE TABLE_NAME = 'SAPUSER'; OWNER  ------------------------------ OPS$PREPRODGEP\GEPADM (optional, to remove all other non usable owner)

12.	CREATE SYNONYM "OPS$<Hostname>\SAPSERVICE<SID>".SAPUSER FOR "OPS$<Hostname>\<SID>ADM".SAPUSER;

13.

GRANT SELECT, UPDATE ON "OPS$<Hostname>\<SID>ADM".SAPUSER TO "OPS$<Hostname>\SAPSERVICE<SID>"; Set the following parameter: REMOTE_OS_AUTHENT = TRUE            in init<sid>.ora. SQL> ALTER SYSTEM SET REMOTE_OS_AUTHENT = TRUE SCOPE=SPFILE; System altered. SQL> COMMIT; RESTART THE DATABASE: Thanks Yoonus