A statement error occurs when an error in executing a database statement occurs in a running program. If such an error occurs, the database system cancels the incorrect statement and issues an error message. The program containing the error is terminated. Furthermore, the transaction is completely canceled in the database (rollback), an ABAP/4 dump is issued, and a message is usually written to the system log. A statement error can also occur if an extensive operation entirely fills up the rollback segment. The reason for such an error is generally incorrect programming. The database administrator does not have to intervene in order to execute a recovery after a statement error.
How to Earn Rs.25000 every month in internet without Investment?
Recovery after Statement Errors
Labels:
SAPDBA Troubleshooting
Subscribe to:
Post Comments (Atom)
topics
-
▼
2009
(764)
-
▼
September
(78)
- Manual Data Source Maintenance
- Automatic Data Capture
- Set-Up Automatic System Landscape Data Capture
- Solution Manager Project Overview
- Project Types
- Edit Products, Product Assignment and Product Vers...
- Solution Manager System Landscape
- Define System Landscape
- System Landscape Check
- Displaying and Managing Existing CPI-C Connections
- Deleting a CPI-C Connection
- Display Gateway Work Processes
- Starting and Stopping the SAP System (Microsoft Wi...
- Starting and Stopping the SAP System (Unix)
- Starting and Stopping Instances
- Memory Management of the SAP Gateway
- Changing Gateway Parameters
- Using the SAP Gateway Outside the SAP System
- Using the SAP Gateway Monitor in the SAP System
- Setting Up Gateway Logging
- Parameterization of the SAP Gateway
- Configuring the SAP Gateway
- Starting and Stopping the SAP Gateway
- Architecture of the SAP Web AS
- Architecture of the SAP Gateway
- SAP Gateway
- SAP DATABASE Partial Recovery
- BRARCHIVE :Mixed Scenario
- BRARCHIVE :Central Scenario
- Special Features of BRRESTORE
- BRARCHIVE :Distributed Scenario
- Special Features of BRARCHIVE
- Supporting the Raw Device Configuration with BRBAC...
- Special Features of BRBACKUP
- ORACLE Databases and Parallel Server Option: Overview
- SAPDBA: Archive mode
- Archiving Parameters
- Automating the Recovery
- SAPDBA Recovery: SYSTEM Tablespace Missing
- SAPDBA Recovery: User Tablespace Missing
- SAPDBA Recovery: One Inactive Online Redo Log Missing
- SAPDBA Recovery: Current Online Redo Log Missing
- SAPDBA Recovery: All Control Files Missing
- Recovery: One Control File Missing
- Error Analysis:sapdba
- Recovery after Media Errors
- Recovery after an Instance Error
- Recovery after an Instance Error
- Recovery after Process Errors
- Recovery after Statement Errors
- Recovery after User Errors
- Types of Database Errors
- SAPDBA: Check (and Repair) Database
- Displaying the Contents of a Spool Request
- List of Spool Requests
- Spool Consistency Check in the Background
- Deleting Multiple Spool Requests Simultaneously
- Adding Spool Requests to Another Spool Request
- Authorizations for Output Devices
- Access Authorizations for the Spool System
- TemSe Data Store
- Avoiding Capacity Problems in TemSe
- Checking Space Usage in TemSe
- Distribution Logs
- Global User Manager
- Creating and Maintaining User Master Records
- Comparing User Master Records
- Setting Up Central User Administration
- Authorization Check in Archiving Programs
- Archive :Authorization Check
- Authorization Check: XML Archiving
- XML Archiving Object
- XML-Based Archiving
- Archiving Object
- ADK-Based Data Archiving
- Data Archiving
- Background documentation System Copy
- Procedure documentationBacking Up and Restoring Yo...
-
▼
September
(78)
No comments:
Post a Comment