SAP Note 25832 - DB2/CS: Termination of R3trans -d aft. installation

Symptom:

After the installation, the system cannot be started with "startsap". R3trans -d
It terminates with an error message. The error message can differ depending on the kernel release. For example:
2EETW000 "I have some problems during TADIR access"
2EETW150 "SAP_DEXT called with msgnr 900:
Internal Error in DB Interface.

or
2EETW169 no connect possible: "DBMS = DB2/6000DB2DBDFT = 'D3E'
--- SYSTEM = '???'."
R3trans finished (0012).

The attempt to log on to the database via command line processor (CLP) as user adm or db2 with the command:
db2 " connect to "

fails with the following SQL error message.
SQL1116N A connection to or activation of database
cannot be made because of BACKUP PENDING. SQLSTATE=57019

Cause and prerequisites

After the database was converted to logretain mode, an offline backup as described in the installation guide was not carried out.

Solution
Unlike other databases, DB2 for AIX does not permit a logon to the database after conversion to logretain mode as long as no offline backup was made. This behavior of the database is useful. However, the error output during a premature attempt to start the SAP System is misleading since it does not refer to the error cause.

The R/3 System can be started after an offline backup of the database was made.

If you only want to activate the database log archiving at a later date, you can deactivate the database parameters LOGRETAIN and USEREXIT via the DB2 administration tools or with the commands
db2 update db cfg for using LOGRETAIN OFF
db2 update db cfg for using USEREXIT OFF

for the time being. Afterwards, a Connect to the database is possible again.
Note that it is not possible to carry out a rollforward recovery of the database as long as the database is not operated in the logretain mode.
Productive R/3 Systems must be operated in the logretain mode.