Chapter 18. Troubleshooting and tracing 383
/SM590000Problem: When you create new application groups, you see the error that is shown in 
Figure 18-4.
Figure 18-4   Error message SQLCODE 497
Reason or resolution: The following actions can help decrease the internal limits:
– If the DBID limit is exceeded, DROP all unused databases and issue a COMMIT.
– If the OBID limit is exceeded, DROP all unused objects in the database and issue a 
COMMIT. Specify a different database, or run the MODIFY utility to reclaim unused OBIDs. 
– Consider dropping indexes on application group data tables for indexes that are not 
frequently used for access. Review NODX reports to identify possible indexes that can 
be dropped. 
– Find any obsolete application groups and related data whose definitions can be 
deleted by using the Administrator Client.
– Analyze application group data tables that became multiple segment tables, and 
change the MAX_ROWS column of the current table in the ARSSEG table to a larger 
value so that another table will not be created.
– Check your application group expiration settings. Ensure that your expiration 
processes are performed on a timely basis. Ensure that your expiration processes 
complete successfully so that application group data segment tables, table spaces, 
and indexes are dropped in DB2 at the same time that the expiration processing 
occurs. 
– Consolidate applications into fewe r application groups, if possible.
– Create another database and modify the ARSUTBL exit to change the default created 
table space to a new database. For more information, see Chapter 11, “Exits” on 
page 241.
– Use Content Manager OnDemand Administrator Client to define application groups to 
go to different databases. 
18.1.4  Monitoring the main server task arssockd
The following problem is common: 
/SM590000Problem: At the start, you need more information about the main server task that is 
named arssockd. 
Reason or resolution: Y ou can now monitor the main server started task arssockd by 
displaying the process usage information for the instance. By using the parameter /-I 
ARC900 -x -p for z/OS, add the following PARM statement to the arssockd started task:
PARM='/-I ARC900 -x -p'
-p displays the process information.
For Content Manager OnDemand, you can monitor the library server from any machine with 
Content Manager OnDemand installed on it by running the following command:
arssockd -I <INSTANCE> -p -x
DB2 z/OS SQLCODE-497 
THE MAXIMUM LIMIT OF INTERNAL IDENTIFIERS HAS BEEN EXCEEDED FOR DATABASE 
<database-name>