Does anyone know what caused the error ‎“%NAT_EXT-E-ADABAS_048, file(s) / user id not available at open time" that prevents any access to the ADABAS database? I got the same error when I tried the ADAORD utility. What should I do to fix this?

The error means, that you need exclusive access to the regarding adabas-file.

To check the user queue type: adaopr db=… file=… di=uq_files

Thanks for the prompt response.

The problem is that I don’t need the exclusive access to the database file. This error happened randomly. Sometimes, only one user cannot access the whole database; sometimes, no one can access the entire database. When it happened to only one user, shutdown and restart the ADABASE will solve the problem. However, if it happed to the entire database for all users, what I did is to restore the database from backup, which results the data lost.

Any better solution to this issue, other than restore the database from backup?

was the database not usable after the restart in the case that all users were getting response 048? What led you to the option of restoring the database?

Have you been able to obtain the subcode for the response 48? ( Are you seeing any errors in the Adabas log? have you run diagnostics on your database?

Individual Natural users can often receive NAT3048 errors when they log into Natural a second time as Natural attempts to use the same userid (configurable in Natural Security).

But if all users are unable to access any files due to response 48’s, it suggests data corruption, so you want to make sure your hardware is ok, you have sufficient space for the various containers (particularly the protection logs).

I suggest you open a support request with Software AG to reduce the chance of further loss of data.

I have very limited experience with ADABAS administration. I don’t know how/where to look at the Adabas log, or run diagnostics on the database. I’ll look at the documentation you suggested about obtaining the subcode for the response 48. Thank you for the information and help!

Utilities are documented here and discusses Adabas Administration.

I’d start with the ADAREP to see what it reports (bad blocks?), followed by ADAVRY to check the logical structure of the database. ADACLP can be used to print out the Adabas command logs.