Basis Check List For System copy Cut/Over

Hacmp Consept

HACMP - High Availiability Clustered Mutiple Processing

The masking or elimination of planned or unplanned downtime
The elimination of single points of failure (SPOFs)
-Computers
-Disks
-Networks
-etc
Fault resilience, but not fault tolerance
A fault tolerant environment has no service interruption
A high availability environment has minimal service interruption

HACMP - Resource Groups
Resource Groups are a set of cluster resources handled as one unit by HACMP, configured by the HACMP administrator.
Attributes of a Resource Group
-startup, fallover and fallback policies
-settling time and the distribution policy
-delayed fallback timer that affects fallback.
-Resource groups can be concurrent and non-concurrent.

Resource Groups are used to coordinate the failover of:
-Network Addresses
-Disks
-NFS mounts
-Applications

Flashcopy Concept

The FlashCopy function enables you to make point-in-time, full volume copies of data, with the copies immediately available for read or write access. You can use the copy with standard backup tools that are available in your environment to create backup copies on tape.
FlashCopy creates a copy of a source volume on the target volume. This copy is called a point-in-time copy. When you initiate a FlashCopy operation, a FlashCopy relationship is created between a source volume and target volume. A FlashCopy relationship is a "mapping" of the FlashCopy source volume and a FlashCopy target volume. This mapping allows a point-in-time copy of that source volume to be copied to the associated target volume. The FlashCopy relationship exists between this volume pair from the time that you initiate a FlashCopy operation until the storage unit copies all data from the source volume to the target volume or you delete the FlashCopy relationship, if it is a persistent FlashCopy.
When the data is physically copied, a background process copies tracks from the source volume to the target volume. The amount of time that it takes to complete the background copy depends on the following criteria:
The amount of data being copied
The number of background copy processes that are occurring
The other activities that are occurring on the DS8000™
FlashCopy supports the following copy options:
Consistency groups
Creates a consistent point-in-time copy of multiple volumes, with negligible host impact. You can enable FlashCopy consistency groups from the command-line interface (DS CLI).
Change recording
Activates the change recording function on the volume pair that is participating in a FlashCopy relationship. This enables a subsequent refresh to the target volume.
Establish FlashCopy on existing Metro Mirror source
Allows you to establish a FlashCopy relationship where the target volume is also the source of an existing remote mirror and copy source volume. This enables you to create full or incremental point-in-time copies at a local site and then use remote mirroring commands to copy the data to the remote site.
Fast reverse
Reverses the FlashCopy relationship without waiting for the finish of the background copy of the previous FlashCopy. This option applies to the Global Mirror mode.
Inhibit writes to target
Ensures that write operations are inhibited on the target volume until a refresh FlashCopy operation is complete.
Multiple Relationship FlashCopy
Allows a source volume to have multiple target volumes at the same time.
Persistent FlashCopy
Allows the FlashCopy relationship to remain even after the FlashCopy operation completes. You must explicitly delete the relationship.
Refresh target volume
Provides the ability to “refresh” a FlashCopy relationship, without recopying all tracks from the source volume to the target volume.
Reverse restore
Reverses the FlashCopy relationship and copies data from the target volume to the source volume.
Reverse FlashCopy relationshipsThe direction of a FlashCopy relationship can be reversed, where the volume that was previously defined as the target becomes the source for the volume that was previously defined as the source (and is now the target). The data that has changed is copied to the volume previously defined as the source.
FlashCopy to Metro Mirror source volumesYou can use an existing Metro Mirror source volume as a FlashCopy target volume. This process allows you to create a point-in-time copy and then make a copy of that data at a remote site.
Multiple relationship FlashCopyThe multiple relationship FlashCopy function allows a source volume to have multiple targets simultaneously.
Persistent FlashCopyA persistent FlashCopy relationship is one that does not end when the background physical copy ends. The relationship persists until it is explicitly withdrawn.
Resynchronization of FlashCopy volume pairsFlashCopy volumes resynchronization (resync) provides the ability to update an initial point-in-time copy of a source volume.
FlashCopy SE featureThe FlashCopy SE feature allocates storage space on an "as-needed" basis by using space on a target volume only when it actually copies tracks from the source volume to the target volume.

SQL error 3113 when access table

Symptom: In T-code ST22
ABAP runtime errors DBIF_RSQL_SQL_ERROR
SQL error 3113 occurred when accessing table "BTCCTL "
Analysis: work process is in re-connect status, seems the WP cannot connect to Database. OSS said it's related with network problem.
Actual Situation: At that certain time, database was set to offline and started a offline backup.

Synchronize SAP Buffer

Sympom: New customized object could not be displayed in the target system after STMS transportation.
Solution: Snchronize the data buffer from T-code command '/SYNC'

RZ10 --> DEFAULT
rdisp/bufrefmode sendoff,exeoff
In a system that has only the central instance, you can deactivate the writing of DDLOG entries:rdisp/bufrefmode = sendoff,exeautoHowever, you must ensure that you reset the setting on the central instance to "sendon,exeauto" when you add at least one additional application server to avoid data inconsistencies in buffered objects.
Buffer invalidation (exeauto) should always be set so that changes to buffered objects that arrive in the system by transports are also synchronized. The setting exeoff is permitted only for test purposes
Note: 14754

Solve error = 12571

FATAL ERROR IN TWO-TASK SERVER: error = 12571Subject: FATAL ERROR IN TWO-TASK SERVER: error = 12571 Found in Alert File Doc ID: Note:164839.1 Type: PROBLEM Last Revision Date: 18-OCT-2007 Status: PUBLISHED

fact: Oracle Server - Enterprise Editionsymptom: Errors appear in alert file symptom: FATAL ERROR IN TWO-TASK SERVER:symptom: ERROR = 12571symptom: trace file generatedsymptom: Database operations continue successfullycause: The most common cause for the above error is an ungraceful disconnection of a session from the oracle db while the db is currently running a dml statement issued by that session. The error is recorded when oracle attempts to reply back to the session with the results of the dml and cannot access the session. Overall database operations are usually not affected.
An ungraceful disconnection could cause by but is not limited to any of the following:- the client machine crashed- the network connection crashed- the user exited the session improperly (not issuing the 'exit' command) - the user application allows the user to exit the application without properly terminating the session.
The above can cause problems with corrupted rollback segments if occurring on a regular basis and is not addressed. This would require db recovery and possibly a db rebuild (not a light matter)
PMON will usually rollback most transactions in the rollback segments for a session if it finds that the session has been ungracefully disconnected, but there is always a chance that it cannot and this will lead to rollback segment corruption.