RFC error: timeout during allocate / CPIC-CALL: ThSAPCMRCV&/ STMS Import

RFC error: timeout during allocate / CPIC-CALL: ThSAPCMRCV&#

Long Text

Dear Support

The system was working fine without any issue for STMS, suddenly

stopped transport system on production system. I tried all the way to

trouble shoot, and I have reconfigured STMS in the landscape but QAS

and DEV are replicating properly. When coming to GBP system throwing

error like

Could not start transport control program tp

RFC error: timeout during allocate / CPIC-CALL:

'ThSAPCMRCV',

Solution:

Also make sure that the TP version is updated to the latest version

available in the service marketplace. Set parameter 

rfc/use_gwstart = 1 in the profile and restart the instance.And restart the instance.

Thanks

Yoonus

[110026] The state 'ManagerSnapshotExists' of the BackupManager does not allow the requested operation SQLSTATE: HY000

[110026] The state 'ManagerSnapshotExists' of the BackupManager does not allow the requested operation SQLSTATE: HY000


select BACKUP_ID from "SYS"."M_BACKUP_CATALOG" where entry_type_name ='complete data backup' and state_name = 'running' order by sys_start_time desc

Execute this comment if any backup running cancel it.

Go tho this SNOTE:

1703435 - Generating a copy of a running instance with database snapshots

Symptom

You want to duplicate a running SAP HANA database by copying the data area.
Comment: As of SAP HANA Support Package Stack 07, the procedure described in this SAP Note for copying a database is no longer recommended. For more information about the recommended database copy procedure, as well as about storage snapshots, see the SAP HANA Administration Guide.

Other Terms

Homogeneous system copy, database snapshot

Reason and Prerequisites

The software of the source database has at least Version 1.00.23. The software version of the target database has to be higher or equal to the software version of the source database.

The system landscapes of the source and target database have to be compatible. This means that the number of nodes and the number and types of services (such as index server) have to match.
The source database must be running, the target database must be offline.
You have to be logged on to the source database with a user who has the BACKUP ADMIN privilege.

Solution

Overview


To duplicate a running SAP HANA database using a copy of the data area, you have to use a database snapshot. A database snapshot is a consistent state that is saved to the data area of the database.

Creating a snapshot

To create a database snapshot in a running SAP HANA database, use the following SQL command:

BACKUP DATA CREATE SNAPSHOT

Take into account that only one database snapshot at a time can exist in an SAP HANA database. This also means that you cannot create a data backup if a database snapshot exists in the SAP HANA database.
If a snapshot already exists, or if a backup is currently running, when you execute the command, the system issues the error message "general error: Backup error: The state 'ManagerSnapshotExists' of the BackupManager does not allow the requested operation".


Removing a snapshot

To remove a database snapshot from a running SAP HANA database, use the following SQL command:

BACKUP DATA DROP SNAPSHOT

If no snapshot exists, calling this command leads to the error message "general error: Backup error: The state 'ManagerIdle' of the BackupManager does not allow the requested operation".

Activating a snapshot

To activate the consistent state that you saved in a database snapshot in the target database, use the following commands:

hdbnsutil -useSnapshot

and

hdbnsutil -convertTopology

hdbnsutil -useSnapshot replaces the current dataset by the dataset that is stored in the database snapshot.

If there is no database snapshot, calling hdbnsutil leads to an error message.

hdbnsutil -convertTopology carries out the required adjustments in the internal structures to the target system.


The database snapshot is removed during activation. As a result, it is neither required nor possible to manually remove the database snapshot in the target database.

Procedure to create a copy of a database using a database snapshot


1. In the source database, create a snapshot using the following SQL command:

BACKUP DATA CREATE SNAPSHOT

2. Copy all the files from the data area of the source database to the respective directory on the target database.
The directory name of the data area is defined in the configuration parameter basepath_datavolumes (in the configuration file global.ini, section persistence).

You have to make sure that the operating system user <SID>adm of the target database has read and write access to the files in the data area of the target database after copying.

3. Delete the snapshot in the source database using the following SQL command:

BACKUP DATA DROP SNAPSHOT

4. In the target database, delete existing file and log backup files.

The directory name for data backup files is defined in the configuration parameter basepath_databackup; the directory name for log backup files is defined in the configuration parameter basepath_logbackup. Both parameters are in the section persistence of the configuration file global.ini.

If in the directory -d $DIR_INSTANCE/../SYS/global/hdb/metadata
the file BackupCatalog.xml exists, delete it.


5. Execute the following commands in a command line environment of the target database:

hdbnsutil -useSnapshot
hdbnsutil -convertTopology

6. Start the target database.


Take into account:

After you activate a database snapshot in the target database, carry out a data backup as soon as possible because a recovery is not possible otherwise.

If a permanent license is installed in the source database, you have to install a new license in the target database.

Renewing SAP Router License & Certificate.

How to Renew The sap router License and Certificate??

You need to remove the old generated files(certreq, cred_v2, local.pse, srcert) from directory xx\usr\sap\saprouter.
from previous certificate request. To do this you can either
rename these files or create a new folder and move these files into it.

Login to the portal and apply the router certificate 

https://websmp204.sap-ag.de/saprouter-sncadd
https://support.sap.com/remote-support/saprouter/saprouter-certificates.html


run below commnat to your saprouter system and generate certificate request file.

Router path:XX:\usr\sap\saprouter


sapgenpse get_pse -v -r certreq -p local.pse  "CN=SAPROUTER, OU=00971xxxxxxx6(My Whatsaap), OU=SAProuter, O=SAP, C=DE"

you will be asked to enter password for security enter your password
======================================================================

C:\usr\sap\saprouter>sapgenpse get_pse -v -r certreq -p local.pse  "CN=SAPROUTER
, OU=xxxxxxx(My Whatsaap), OU=SAProuter, O=SAP, C=DE"
Got absolute PSE path "C:\usr\sap\saprouter\local.pse".
Please enter PSE PIN/Passphrase: *********
Please reenter PSE PIN/Passphrase: *********

!!! WARNING: For security reasons it is recommended to use a PIN/passphrase
!!! WARNING: which is at least 8 characters long and contains characters in
!!! WARNING: upper and lower case, numbers and non-alphanumeric symbols.

 Supplied distinguished name: "CN=SAPROUTER, OU=009715xxxxxx(My Whatsaap), OU=SAProuter, O=SAP,
 C=DE"
 Creating PSE with format v2 (default)
 succeeded.
 certificate creation... ok
 PSE update... ok
 PKRoot... ok
Generating certificate request... ok.

Two file will be created local.pse and certreq.
Open certreq file and copy past to SMP certificate request colum and proceed next  then it be will generated your certificate.
Copy your certificate key to scert file and import to local.pse using the following command
===========================================================================================

C:\usr\sap\saprouter>sapgenpse import_own_cert -c C:\usr\sap\saprouter\srcert -p
 C:\usr\sap\saprouter\local.pse
Please enter PSE PIN/Passphrase: *********
CA-Response successfully imported into PSE "C:\usr\sap\saprouter\local.pse"

Now you have to create the credentials for the SAProuter with the same program.
This will create a file called “cred_v2″ in the same directory as “local.pse”

use the below command to run this
=================================================================================

C:\usr\sap\saprouter>sapgenpse seclogin -p C:\usr\sap\saprouter\local.pse -O sap
routeradmin
 running seclogin with USER="SAPRouterAdmin"
 creating credentials for user "SAPROUTER\SAPRouterAdmin" (yourself)...
Please enter PSE PIN/Passphrase: *********
 Adjusting credentials and PSE ACLs to include "SAPROUTER\SAPRouterAdmin"...
 Oh, you supplied your own name explicitly ... ok.
   C:\usr\sap\saprouter\cred_v2  ... ok.
   C:\usr\sap\saprouter\local.pse  ... ok.
 Added SSO-credentials for PSE "C:\usr\sap\saprouter\local.pse"


 To check if the certificate has been imported successfully, run the following command
 ================================================================================

 sapgenpse get_my_name -v -n Issuer

 C:\usr\sap\saprouter>sapgenpse get_my_name -v -n Issuer
 Opening PSE "C:\usr\sap\saprouter\local.pse"...
 PSE (v2) open ok.
 Retrieving my certificate... ok.
 Getting requested information... ok.
SSO for USER "SAPRouterAdmin"
  with PSE file "C:\usr\sap\saprouter\local.pse"

Issuer     : CN=SAProuter CA, OU=SAProuter, O=SAP Trust Community II, C=DE


By executing follwing command you can see the renewed license validity
=========================================================================

sapgenpse get_my_name -v -n validity

C:\usr\sap\saprouter>sapgenpse get_my_name -v -n validity
 Opening PSE "C:\usr\sap\saprouter\local.pse"...
 PSE (v2) open ok.
 Retrieving my certificate... ok.
 Getting requested information... ok.
SSO for USER "SAPRouterAdmin"
  with PSE file "C:\usr\sap\saprouter\local.pse"

Validity  -  NotBefore:   Sat Jun 25 09:52:11 2016 (160625055211Z)
             NotAfter :   Sun Jun 25 09:52:11 2017 (170625055211Z)


Thanks
Yoonus

SAP ORACLE LOG FILE SWITCHING!!!!!!!!!!!!!!! INCREASE LOG FILE SIZE TO 150MB

 For the optimum performance you can increase the size of redo log filze size up to 150 MB , here I am going to discribe  online redo log migration from 50 MB to 150MB.

The Redo Logs must be dropped and recreated for changing the redo log size. It can be done online without shutting down the database. However, you need to make sure that the Redo Group being dropped should be INACTIVE when you do this.

Check Redo Log group and Status:
SQL> Select group#, status from v$log;
    GROUP# STATUS
---------- ----------------
         1 ACTIVE
         2 ACTIVE
         3 CURRENT

         4 ACTIVE
SQL> select group#,members,status,bytes/1024/1024 as mb from v$log;

    GROUP#    MEMBERS STATUS       MB
---------- ---------- ---------------- ----------
         1          2 ACTIVE                          50
         2          2 ACTIVE                         50
         3          2 CURRENT                     50
         4          2 ACTIVE                         50

Check the log file locationm group, and status

SQL>select * from v$logfile;

Group     Status                 Location
4 ONLINE E:\ORACLE\GEP\ORIGLOGB\LOG_G14M1.DBF
4 ONLINE F:\ORACLE\GEP\MIRRLOGB\LOG_G14M2.DBF
3 ONLINE E:\ORACLE\GEP\ORIGLOGA\LOG_G13M1.DBF
3 ONLINE F:\ORACLE\GEP\MIRRLOGA\LOG_G13M2.DBF
2 ONLINE E:\ORACLE\GEP\ORIGLOGB\LOG_G12M1.DBF
2 ONLINE F:\ORACLE\GEP\MIRRLOGB\LOG_G12M2.DBF
1 ONLINE E:\ORACLE\GEP\ORIGLOGA\LOG_G11M1.DBF

1 ONLINE F:\ORACLE\GEP\MIRRLOGA\LOG_G11M2.DBF


#--SQL> select group#,members,status,bytes/1024/1024 as mb from v$log;


    GROUP#    MEMBERS STATUS                   MB
---------- ---------- ---------------- ----------
         1          2 INACTIVE                150
         2          2 INACTIVE                150
         3          2 CURRENT                 150
         4          2 ACTIVE                   50
         5          2 INACTIVE                150
         6          2 INACTIVE                150
         7          4 INACTIVE                150

#--7 rows selected.

alter system checkpoint;

ALTER SYSTEM CHECKPOINT GLOBAL;

SQL> ALTER SYSTEM CHECKPOINT GLOBAL;

System altered.

--SQL> select group#,members,status,bytes/1024/1024 as mb from v$log;

    GROUP#    MEMBERS STATUS                   MB
---------- ---------- ---------------- ----------
         1          2 INACTIVE                150
         2          2 INACTIVE                150
         3          2 CURRENT                 150
         4          2 INACTIVE                 50
         5          2 INACTIVE                150
         6          2 INACTIVE                150
         7          4 INACTIVE                150

--7 rows selected.




 alter system switch logfile;


ALTER DATABASE DROP LOGFILE GROUP 1;

alter database ADD  logfile GROUP 1 ('F:\ORACLE\GEP\MIRRLOGB\LOG150N_G14M2.DBF','F:\ORACLE\GEP\MIRRLOGB\LOG150N_G12M2.DBF') SIZE 150M REUSE

alter system switch logfile;


ALTER DATABASE DROP LOGFILE GROUP 2;


alter database ADD  logfile GROUP 2 ('F:\ORACLE\GEP\MIRRLOGB\LOG150N_G11M2.DBF','E:\ORACLE\GEP\ORIGLOGB\LOG150N_G12M1.DBF') SIZE 150M REUSE;

alter system switch logfile;


ALTER DATABASE DROP LOGFILE GROUP 3;


alter database ADD  logfile GROUP 3 ('E:\ORACLE\GEP\ORIGLOGA\LOG150N_G13M1.DBF','F:\ORACLE\GEP\MIRRLOGA\LOG150N_G13M2.DBF') SIZE 150M REUSE;

alter system switch logfile;


ALTER DATABASE DROP LOGFILE GROUP 4;


alter database ADD  logfile GROUP 4 ('E:\ORACLE\GEP\ORIGLOGB\LOG150N_G14M1.DBF','F:\ORACLE\GEP\MIRRLOGB\LOG150N_G11M1.DBF') SIZE 150M REUSE;


alter system switch logfile;


Complete!

refer this: https://muneer2908.wordpress.com/2011/01/27/how-to-change-the-redo-log-file-size-in-oracle-database/