R3load.exe -i SAPSPROT.cmd -dbcodepage 4103 -l SAPSPROT.log -stop_on_error Loading of 'SAPSSEXC' import package is interrupted with R3load error.

Error 1

0

IMPORT_ABAP Error. Loading of 'SAPSSEXC' import package is interrupted with R3load error.

Error 2

2EETW169 no connect possible: "connect failed with DBLI_RC_LOAD_LIB_FAILED."

Error 3
SAP Java Server VM (build 6.1.068 24.55-b13, Jun 22 2014 00:31:35 - 61_REL - optU - windows amd64 - 6 - bas2:220276 (mixed mode))
Import Monitor jobs: running 1, waiting 8, completed 19, failed 0, total 28.
Import Monitor jobs: running 2, waiting 7, completed 19, failed 0, total 28.
Import Monitor jobs: running 3, waiting 6, completed 19, failed 0, total 28.
Import Monitor jobs: running 4, waiting 5, completed 19, failed 0, total 28.
Import Monitor jobs: running 5, waiting 4, completed 19, failed 0, total 28.
Import Monitor jobs: running 6, waiting 3, completed 19, failed 0, total 28.
Import Monitor jobs: running 7, waiting 2, completed 19, failed 0, total 28.
Import Monitor jobs: running 8, waiting 1, completed 19, failed 0, total 28.
Loading of 'SAPSLOAD' import package: ERROR
Import Monitor jobs: running 7, waiting 1, completed 19, failed 1, total 28.
Loading of 'SAPSSRC' import package: ERROR
Import Monitor jobs: running 6, waiting 1, completed 19, failed 2, total 28.
Loading of 'SAPAPPL1' import package: ERROR
Import Monitor jobs: running 5, waiting 1, completed 19, failed 3, total 28.
Loading of 'SAPAPPL0' import package: ERROR
Import Monitor jobs: running 4, waiting 1, completed 19, failed 4, total 28.
Loading of 'SAPSSEXC' import package: ERROR
Import Monitor jobs: running 3, waiting 1, completed 19, failed 5, total 28.
Loading of 'SAPAPPL2' import package: ERROR
Import Monitor jobs: running 2, waiting 1, completed 19, failed 6, total 28.
Loading of 'SAPSDIC' import package: ERROR
Import Monitor jobs: running 1, waiting 1, completed 19, failed 7, total 28.
Loading of 'SAPSPROT' import package: ERROR
Import Monitor jobs: running 0, waiting 1, completed 19, failed 8, total 28.
================
Error 4
C:\usr\sap\GEP\SYS\exe\uc\NTAMD64\R3load.exe -ctf I C:\INST\SAP_-ECC6.FULL DUMP\Inst_Export\DATA_UNITS\EXPORT_11\DATA\SAPSSRC.STR C:\Program Files\sapinst_instdir\BS2008\ERP604\AS-ABAP\ORA\CENTRAL\DDLORA.TPL SAPSSRC.TSK ORA -l SAPSSRC.log
Error 4
C:\usr\sap\GEP\SYS\exe\uc\NTAMD64\R3load.exe: job completed
C:\usr\sap\GEP\SYS\exe\uc\NTAMD64\R3load.exe: END OF LOG: 20180510121345
C:\usr\sap\GEP\SYS\exe\uc\NTAMD64\R3load.exe: START OF LOG: 20180510121345
C:\usr\sap\GEP\SYS\exe\uc\NTAMD64\R3load.exe: sccsid @(#) $Id: //bas/720_REL/src/R3ld/R3load/R3ldmain.c#3 $ SAP
C:\usr\sap\GEP\SYS\exe\uc\NTAMD64\R3load.exe: version R7.20/V1.4 [UNICODE]
Compiled May  7 2010 03:19:51
C:\usr\sap\GEP\SYS\exe\uc\NTAMD64\R3load.exe -i SAPSSRC.cmd -dbcodepage 4103 -l SAPSSRC.log -stop_on_error
DbSl Trace: ORA-942 when accessing table SAPUSER

Error 6

TRACE      2018-05-14 12:39:45.313 [syxxcfile.cpp:85]
           CSyFileImpl::decideIfMoveCopyNode(const CopyMoveDestinationInfo & {m_nodeTypeForCombiCheck: ..., m_path: C:/Program Files/sapinst_instdir/BS2008/ERP604/AS-ABAP/ORA/CENTRAL/__instana_tmp.11.xml, m_realNodeType: 8}, ISyNode::CopyMoveMode_t 0x3, PSyNodeInt &) const 
           lib=syslib module=syslib
Target node does not exist and (mode & ISyNode::MISSING) ==> I will copy/move.

Loading of 'SAPSSEXC' import package is interrupted with R3load error.


Solution:

One:
execute r3loade.exe if throwing an error msvcr120.dll missing
to apply this download vcredist_x64 https://www.microsoft.com/en-us/download/details.aspx?id=40784

Two:

Check below environment values are set properly

dba_ora_schema
dbms_type
ORACLE_HOME
SAPDATA_HOME
ORACLE_SID
RSEC_SSFS_DATAPATH
RSEC_SSFS_KEYPATH

Three:

check the BRTOOL version which support the database version and instant client versions.

Most probably issue is SAPSR3 user is getting locked while trying to importabap . Avoid this  Unlock the user


SQL> select username ,account_status  from dba_users;

SAPSR3                                                                         
LOCKED(TIMED)  

SQL> alter user sapsr3 account unlock;

The execute the below comment to avoid  locking again:


ALTER PROFILE DEFAULT LIMIT FAILED_LOGIN_ATTEMPTS UNLIMITED;

Refer the snote: 951167 - ORA-28000: the account is locked

Symptom

You cannot log on to the Oracle database and the program returns the message:

ORA-28000: the account is locked

Other Terms

Reason and Prerequisites

ORA-28000 is usually triggered because someone has previously attempted to log on several times using an incorrect password, which causes the logon to fail and returns ORA-01017. The number of allowed logon attempts is defined by the resource FAILED_LOGIN_ATTEMPTS in the profile. You can determine the current value of this parameter using the following query:

SELECT LIMIT FROM DBA_PROFILES
WHERE
  PROFILE = 'DEFAULT' AND
  RESOURCE_NAME = 'FAILED_LOGIN_ATTEMPTS';

Until Oracle 10.1, this parameter had the default value UNLIMITED, so that no ORA-28000 messages would normally occur. As of Oracle 10.2, this standard value has been set to 10.

A further option in the case of a locked user is an explicit lock as follows:

ALTER USER <username> ACCOUNT LOCK;

Solution

To prevent ORA-28000 errors, and avoid similar problems in future, be aware of the following:

• If you use Oracle 9i or earlier, do not manually restrict the authorizations of the default profile (also refer to Note 700548 (16)).

• If FAILED_LOGIN_ATTEMPTS is not set to UNLIMITED, you can adjust it as follows:
  
  ALTER PROFILE DEFAULT LIMIT FAILED_LOGIN_ATTEMPTS UNLIMITED;

           This is also possible for Oracle 10. 1 and earlier and Oracle 10.2 and later.

• If a user is already locked, you can unlock it as follows:
  
  ALTER USER <username> ACCOUNT UNLOCK;

           If the ORA-28000 error occurred due to a large number of failed logon attempts, you must check why these logon attempts were unsuccessful and returned the ORA-01017 error. The cause is often an incorrect configuration of the OPS$ mechanism. In this case, refer to Note 400241.

 
Thanks
Yoonus

--- dbs_ora_tnsname , TNS-03505: Failed to resolve name

C:\Users\SAPadm>r3trans -x
This is r3trans version 6.24 (release 722 - 24.03.17 - 20:17:03).
unicode enabled version
R3trans=>sapparam(1c): No Profile used.
R3trans=>sapparam: SAPSYSTEMNAME neither in Profile nor in Commandline
2EETW169 no connect possible: "DBMS = ORACLE                           --- dbs_ora_tnsname = 'EEP'"
r3trans finished (0012).

Solution:

Correct the  TNS file entry and SQLnet.ora file.

entry missing in TNSNAME.ora





C:\Users\SApadm>tnsping EEP
TNS Ping Utility for 64-bit Windows: Version 12.1.0.2.0 - Production on 09-MAY-2018 12:06:57
Copyright (c) 1997, 2014, Oracle.  All rights reserved.
Used parameter files:
C:\usr\sap\EEP\SYS\profile\oracle\sqlnet.ora
TNS-03505: Failed to resolve name






THANKS
yOONUS