You want to check whether the definitions of tables that are relevant for the code page administration, spooler or TemSe can be used in the C programs and database.
Why?
We suspected that the problem was here.
Messages appeared: SysLog F5G or SysLog F8T.
Software does not match the DD:
RSCP, RSTS, RSPO, rscpgdio.c, rspogdio.c, NameTab
This comparison compares two pages:
The first page:
The table structures that recognize the C programs. They entered the programs during the compilation and mounting stage (for example, the R/3 C kernel).
The second page:
The structures in the current database. Here, there are table structures on four levels:
- 1. The database itself (for transparent tables). This can be viewed with SQL using a DESCR command.
- 2. SAP Data Dictionary. Displayed with transaction SE11
- 3. The "NameTab". This contains an extract from the SAP Data Dictionary and is generated during "activation" and stored back in the database.
- 4. The "NameTab buffer". This stores excerpts from the NameTab at runtime in order to improve access times.
The comparisons described here refer to level 4: the NameTab buffer.
Why can discrepancies occur?
- Software from another release was started.
- The tables were not successfully activated when changes are imported.
- Some inconsistencies occurred between the database and C program (for example, the SAP kernel) when changes were implemented.
- The NameTab buffer was overwritten.
- Critical tables were modified without authorization.
Determine the reason for the problem. The next steps depend on this.
- Software from another release was started.
The kernel accesses all affected tables. However, programs such as "R3trans", "R3load", "rscpf_db" and others must read some of these tables.
- The tables were not successfully activated when changes are imported.
The table name is specified in the error message. In transaction SE11, check whether the corresponding table or structure is active.
- Some inconsistencies occurred between the database and the C program when changes were imported.
In fact, this should not happen even once during the beta test phase. If it does, refer to the attachment. If no explanation is provided there, ask SAP which components are affected and which restrictions apply.
- The NameTab buffer was overwritten.
You can carry out a direct comparison between level 2 and 3 in transaction SE11. There is no check on the NameTab buffer (Level 4). Usually, no errors occur here in any case. The OK code "/$SYNC" resets this buffer. If this eliminates the errors, you can check the memory management.
- Critical tables were modified without authorization.
The C-programs only recognize a few tables. However, these tables can only be changed in a very limited way. No other changes are authorized, so must be undone if problems occur.
There is a way of displaying the checks that are run in connection with this note:
- 1. Determine the directory with the current software: This is, in general, '/usr/sap/C11/SYS/exe/run'. 'C11' should be replaced with the system name ("sid") in this case. Control: cd /usr/sap/C11/D*/work
ls -l dw.sap*In this case, find two programs: "disp+work", "rscpf_db".
- 2. Determine the current profile: cd /usr/sap/C11/D*/work
head stderr1
- 3. Ask for the code page administration: .../rscpf_db pf=... tchk -v
| |
| +---- current profile
+---- path name for the programs
Naturally, the 'rscpf_db' program must be as current as the kernel.
Appendix: Special cases of tables and fieldsUMGSETTING
The fields from item 14 are optional. If they exist, they should occur in the sequence NTABU, TRANS, EINDX.
A warning here does not disrupt normal operation. Some special functions do not work, only when the database is converted to Unicode.
UMGPMIG
The field at position 25 is optional. If it exists, it should be called SCANTIME.
A warning here does not disrupt operation because this field is not used by a C program. As of the following kernel patch levels, the message F5G for table UMGPMIG is no longer displayed:
| 620 | Kernel patch level | 1800 |
| R3load | 67 | |
| 640 | Kernel patch level | 56 |
| R3load | 26 |
No comments:
Post a Comment