Monday, December 15, 2003
SE14
There is an awful lot of stuff in SE14, which should let you manipulate tables from within SAP rather than at database or sapdba level.
It's best to change the values of next and max extents here, rather than in sapdba. The reason is that if the table is busy when you try to apply the change, you can just hit re-execute to try again, and again, and again....; don't worry about all the messages in the system log and database alert log that you generate!
You can also check here that SAP and the database both think the table has the same structure - particularly useful if you've transported changes to data elements or domains that are defined in the table. Watch out for BSEG - it's a b@gger.
You can reactivate the table, and also check if previous activations have been successful. Look at the options on the main SE14 screen, before you've even entered a table name.
There is an awful lot of stuff in SE14, which should let you manipulate tables from within SAP rather than at database or sapdba level.
It's best to change the values of next and max extents here, rather than in sapdba. The reason is that if the table is busy when you try to apply the change, you can just hit re-execute to try again, and again, and again....; don't worry about all the messages in the system log and database alert log that you generate!
You can also check here that SAP and the database both think the table has the same structure - particularly useful if you've transported changes to data elements or domains that are defined in the table. Watch out for BSEG - it's a b@gger.
You can reactivate the table, and also check if previous activations have been successful. Look at the options on the main SE14 screen, before you've even entered a table name.
Comments:
Post a Comment
