KB article 1765090 is related to this feature request.
Sequence of events: ADASAV back up database; ADADBS delete all application files; ADAORD REORDB; ADASAV restore FMOVE all application files (expanded files in the database) back into database. Normally, this type of database maintenance is followed by IPL. IPL didn't take place this time due to special data center event. We observed many jobs transactions abended with 3160. We understand that The ADARSP160 indicates that more than 35 ASSO or DATA blocks are in use for a single command. For an expanded file chain, Adabas adjusts this calculation only at nucleus initialization.
To solve the database had to be brought down and back up.
Use Case | HA |
Created on Brainstorm | 09.20.2016 04:20 pm |
Brainstorm ID | 4015 |