cancel
Showing results for 
Search instead for 
Did you mean: 

export migration from DB6 (DB2 UDB) on AIX with SAPR3 scheme

Former Member
0 Kudos

dear all,

I'm having a problem during the export phase.

This is the error I'm facing

Caught ESAPinstException in module call: Assertion failed: in

function (role, readAccountData) {

    if (readAccountData === undefined) {

        readAccountData = true;

    }

    NWUsers.trace("NWUsers.getAccountData(", role, ")");

    this._initAccountData();

    ASSERT(arguments.callee, this.haveAccountData(role), "role " + role + " is not created yet.");

    var ad = this._readAccountDataFromKeydb(role);

    if (readAccountData) {

        ad = this._readAccountData(ad);

    }

    var masterpwd = this.getMasterPassword();

    if (ad.password == "" && this._useMasterPasswordForAccountData(ad) && ad.type == "USER" && masterpwd !== undefined && role != NWUsers.roles.J2EEGuest && !ad.locked) {

        ad.password = masterpwd;

    }

    NWUsers.trace("NWUsers.getAccountData(): ", dump_properties(ad));

    return ad;

}

: role SAPSID is not created yet..

I suppose the problem is releated to my scheme thar is SAPR3. It seems a bug of the procedere that requires SAPSID role.

Someone of you encounterd this error?

any help?

Accepted Solutions (1)

Accepted Solutions (1)

Former Member
0 Kudos

Hi all,

I have discovered the root case. under the default profile there are reference to j2ee parameters coming from the original system that was splitted  in Abap and Java.

After deleting the lines referencing to j2ee the step went ahead

Answers (1)

Answers (1)

former_member264034
Active Contributor
0 Kudos

Hi,

Is this user sap<sid> created locally?

If yes, has the user been created through sapinst or manually?

This user is the ABAP database connect user and should be in the database
maintenance group.

In the event that the user does not exist locally, could you please try
creating it manually according to the installation guide chapter
"Users and Groups" (search for sap<sapsid>)?

Once that is completed, retry the installation step again.

See SAP note 1276022 - SAP Solution Manager 7.0 EHP1 Installation

Regards,
Aidan

Former Member
0 Kudos

hello Aidan,

the problem is that the default user is not SAPSID. This is an old release upgradated to EHP6.

The scheme name so is SAPR3 (5 letters) and not 6 as per new installation.

As per your experience SAP<SID> should be created manuallY for any reason?