Database option 'trunc log on chkpt' to 'true' for the SUM process

Issue:

During Upgrade step to start "Execution" and the process tells me: WARNING: 'Database log mode' will not be changed automatically. If you want to disable archiving now, set database option 'trunc log on' to 'true' for the XXX database.
Error occured in Sybase ASE.


Resolution:

To modify the log mode on Sybase ASE, you have to follow further steps :

1. Log in on your server with user syb

2. Launch with a command line tool to connect to ASE database

> isql -Usapsa -P< password > -S< SID > -X

3. On the SQL interface, enter the statements to change log mode

1> use master

2> go

1> sp_dboption <SID>, 'trunc',true

2> go

Database option 'trunc. log on chkpt.' turned OFF for database ''.

Running CHECKPOINT on database '' for option 'trunc. log on chkpt.' to take

effect.

(return status = 0)

1> checkpoint

2> go

After finish the Upgrade change the Setting "true" to "false".

1. Log in on your server with user syb

2. Launch with a command-line tool to connect to ASE database

> isql -Usapsa -P< password > -S< SID > -X
3. On the SQL interface, enter the statements to change log mode

1> use master

2> go

1> sp_dboption <SID> , 'trunc',false

2> go

Database option 'trunc. log on chkpt.' turned OFF for database ''.

Running CHECKPOINT on database '' for option 'trunc. log on chkpt.' to take

effect.

(return status = 0)

1> checkpoint

2> go

This command will ensure that everytime a checkpoint comes along, the Sybase dataserver engine will truncate the transaction log. You should not do this on a production server, as the transaction log is used for performing a complete restoration of data.  You may want to do this when you don't have enough space for keeping transaction data, like on a quality server or development server. 

Stop Running SAP Transport Request(TR).

Steps for stop running TR in SAP.

1.  Execute transaction code STMS_IMPORT.
     Select Goto > Import Monitor.
    Under Execution, Select the transport and right click.
    Choose on Delete entry to stop the running transport.

2. Now Running Transport Request Stoped and redy to Import.

SAP Solution manager USER_AUTH_FAILED - SLD authorization issue

Symptom

Error: USER_AUTH_FAILED when entering the username and password? to logon to local SLD.

Environment

    SAP Solution Manager 7.1
    SAP Solution Manager 7.2

Reproducing the Issue

    Execute transaction Solman_Setup.
    Select System Preparation -> Prepare Landscape Description -> step Select SLD (Solution Manager 7.1)
    or Infrastructure Preparation -> Set Up Landscape Management -> step SLD Connections (Solution Manager 7.2)
    Click the Button 'Select Local SLD' where you enter a Username and Password
    Results with USER_AUTH_FAILED.

Cause

Missing authorization for the user which is used to logon to SLD. The user should be a system user too.

Resolution

SAP recommends to use the user 'SLDDSUSER' in step Select SLD (Solution Manager 7.1) / SLD connections (Solution Manager 7.2).
The user SLDDSUSER in the SAP Solution Manager is required by the SLD data suppliers to write technical system information into SLD.

The user in step Select SLD (Solution Manager 7.1) / SLD connections (Solution Manager 7.2) requires UME role: SAP_SLD_DATA_SUPPLIER to create, modify and delete CIM instances of the landscape description subset as a data supplier without access to the SLD User Interface.
For an SLD as of release SAP NetWeaver 7.1 user needs also the role SAP_SLD_CONTENT_SYNC.
For an SLD as of release SAP NetWeaver 7.0 user at least needs the role SAP_SLD_GUEST.

This user should be defined as a System User.