SAP Note 11515 - Shrinking/deleting rollback tablespaces.

-
Symptom

The customer wants to shrink tablespace PSAPROLL, as it was defined too large.

Cause and prerequisites

Tablespace PSAPROLL defined too large.

Solution
Important: - This note applies only to ORACLE7 and Oracle8!!!
- The storage parameter OPTIMAL is NOT exported.
You have to activate it manually afterwards

sqldba lmode=y
connect internal
alter rollback segment storage (optimal xxM);

1. Determine the datafiles that belong to tablespace PSAPROLL
sqlplus sapr3/sap
SQL> select file_name from dba_data_files
where tablespace_name = 'PSAPROLL';

2. Structure export of the complete database (no table contents!!)
using ORACLE tool exp:

exp system/manager

The user is then prompted, and can use the default settings for
all questions except for the following three:

(1)E(ntire database), (2)U(sers), or (3)T(ables): (2)U > 1
Export table data (yes/no): yes > no
Compress extents (yes/no): yes > no

CAUTION: If statistics were already created for tables, these must
either be deleted beforehand or the export must be called
in a command procedure.

Otherwise the time estimate will not be correct!!

exp system/manager file=expges.dmp full=y compress=n
statistics=none buffer=1000 rows=n


3. sqldba lmode=y (connect internal)
SQLDBA> create rollback segment dummy storage (initial 32K);

4. SQLDBA> alter rollback segment dummy online;
5. SQLDBA> alter rollback segment prs_ offline; (x stands for 1,2,3,...,n). All rollback segments
must be set offline. Active rollback segments in the DB
can be listed under the init.ora parameter
rollback_segments.
6. SQLDBA> drop rollback segment prs_ ; (x stands for 1,2,3,...,10) - all rollback segments must
be dropped (see step 5)

7. SQLDBA> drop tablespace psaproll including contents;

8. Once step 7 has been performed successfully, the data files
determined in step 1 can be deleted at UNIX level .

9. You must now redefine tablespace PSAPROLL:
Example:
sqldba lmode=y (connect internal)
SQLDBA> create tablespace psaproll
datafile '/usr/ora/C11/sapdata0/roll_1/roll.data1'
size 200M;

10. Structure import of the database exported in step 2, using
ORACLE tool imp:

imp system/manager

The user is prompted again and can use the default responses to
all questions with the exception of the following:

Import table data (yes/no): yes > no

Time required: 5-10 minutes

In this way you can avoid creating the individual rollback segments
manually. All the other structures of the export file already
exist and are no longer imported.
11. Shut down / restart the database.

12. sqldba lmode=y (connect internal)
SQLDBA> drop rollback segment dummy;

Key word: PSAPROLL

Comments

Post a Comment

Popular posts from this blog

SAP Note 11489 - What to do when there are print problems in QM.

-
Symptom Either an incorrect inspection instruction or sample drawing instruc- tion is printed, or none at all. Errors in the print control settings in the Customizing application cannot be ruled out. If no inspection instruction or sample drawing instruction is printed, two different situations can exist: a) In the inspection lot transactions, no sample drawing instruction or inspection instruction can be printed after the sample has been calculated. b) In the inspection lot transactions, the documents can be printed, but not immediately from the stock postings. Error messages: QA162, CO412 (among others) Transaction codes: QA01, QA02, QA03, MB01 (among others) Cause and prerequisites There can be several reasons for this situation: 1. The print form does not exist, the print form does not exist in the required language nor does it exist in the client concerned, or the print form is not activated (system installation). 2. The table settings are incorrect (Customizing...
Read more

SAP Note 11507 - Fields returned wrong in elec. bank statement.

-
Symptom The bank sends an incorrect business transaction code. This code does not exist in the system. It is not possible to process the corresonding line in the electronic bank statement. Cause and prerequisites Bank error Solution Either a) or b) a) Temporarily define the incorrect business transaction code in the system, process the statement, then delete the transaction code afterwards. b) Change the business transaction code in the database: 1.) Transaction : SE16 Table : FEBKO Application : 0001 Sender bank : 'Bank code' (15-digit) 'Account number' Statemnt ID : 'Year'(4-digit) 'Statement number'(5-digit) ShortKey : select "Output" --> Note the displayed ShortKey! 2.) Transaction : SE16 Table : FEBEP ShortKey : noted value BusTransCode : select "Output" --> Note the incorrect BusTr...
Read more

SAP Note 11477 - Check deposit: fields are not printed.

-
Symptom You want to print out more fields than those specified in the standard form, F_M40S_CHEQUE, on the check deposit list (for example, FEBSCK-KUNNR = Customer number, ...). Cause and prerequisites Outputting other fields on the check deposit form is not supported. Output is not possible for most fields because the relationship between form and check is not 1:1, but instead N:1. For example, one check could be used to pay the invoices of several customers. In addition to the fields available in the standard form, the fields in table FEBEP can be output for each check. However, only a few of the fields in FEBEP are filled. Solution If organizational measures can guarantee a 1:1 relationship, you can enter the required field in the "Issuer" field manually and print it on the form. Of course, you can do this only if you are not using the "Issuer" field. Additional key words SAPMF40S, FF68
Read more