- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - OpenVMS
- >
- Re: ABS_CATLG_00001 process
Categories
Company
Local Language
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Discussions
Discussions
Forums
Forums
Discussions
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
- BladeSystem Infrastructure and Application Solutions
- Appliance Servers
- Alpha Servers
- BackOffice Products
- Internet Products
- HPE 9000 and HPE e3000 Servers
- Networking
- Netservers
- Secure OS Software for Linux
- Server Management (Insight Manager 7)
- Windows Server 2003
- Operating System - Tru64 Unix
- ProLiant Deployment and Provisioning
- Linux-Based Community / Regional
- Microsoft System Center Integration
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Community
Resources
Forums
Blogs
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО10-02-2007 04:20 AM
тАО10-02-2007 04:20 AM
Solution$ MDMS SET CATALOG SRAY_CATALOG/NOSTAGING
It should not even allow staging for a DISK type catalog. That should be changed...but not by me anymore.
The ABS_CATLG_nnnn processes are created (with $CREPRC) at the end of the save operation by the ABS coordinator process and not through MDMS' scheduling feature.
One of the SAVE logfiles should contain the log for creating ABS_CATLG_00001. Maybe this is not for a SAVE using CATALOG SRAY_CATALOG?
Use SDA SHOW PROCESS/CHANNEL on this process and look for a .DAT and .LOG file it has open. It may give more information on what this process is doing.
You cannot have a SAVE/ARCHIVE without a CATALOG. In case of catalog type DISKS only the save set information is stored in the catalog...no individual infromation of files saved. This catalog type produces very small catalog files.
/Guenther
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО10-02-2007 04:32 AM
тАО10-02-2007 04:32 AM
Re: ABS_CATLG_00001 process
00:22:15 COORD: Staging process PID : 20403E01
00:22:15 COORD: Staging catalog : ABS$CATALOG:1MONTH_99_1.STG;1
00:22:15 COORD: Staging procedure : ABS$CATALOG:1MONTH_99_1_1.COM;1
00:22:15 COORD: Staging logfile : ABS$LOG:1MONTH_99_1.LOG
00:22:31 THREAD #1: Normal successful completion
You get the PID of the process and not the name. Sorry my memory has fainted a bit on ABS...
/Guenther
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО10-02-2007 06:53 AM
тАО10-02-2007 06:53 AM
Re: ABS_CATLG_00001 process
I've searched all of my ABS log files and I don't see any of them that have a reference to abs_catlg. I do see in the save request log files where the staging process is kicked off though.
What confuses me most is what this abs_catlg_0000n process is doing for hours at at time. If I'm using a catalog of type disks, then shouldn't any catlog processing take mere seconds/minutes to complete?
The abs_catlg process appears to be happening on Sunday mornings, so I will watch for it then and see what SDA can tell me if I can catch it running.
Thanks.
Regards,
Trace
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО10-02-2007 07:07 AM
тАО10-02-2007 07:07 AM
Re: ABS_CATLG_00001 process
$mdms show catalog/full abs_catalog
Catalog Name: ABS_CATALOG
Catalog Node: SRAY7
Access Control: NONE
Directory: ABS$ROOT:[CATALOG]
Last Cleaned: 02-OCT-2007 12:30:01
Owner: ABS
Staging : YES
Type: FILES
This must be kicking off the abs_catlg process. However, the log files for the staging process only take a few minutes to complete.
I'm sure I'm getting close now. Thanks Guenther!
Regards,
Trace
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО10-03-2007 03:26 AM
тАО10-03-2007 03:26 AM
Re: ABS_CATLG_00001 process
The ABS_LOCAL directory and all of its contents are things that I set up. It does not come standard with the ABS install.
I found that I wanted to put a number of ABS related command procedures such as login, environment prologue and epilogue procedures, monthly catalog tuning procedures, etc ... all in one place but NOT in the standard ABS directories. That way I can easily maintain my own procedures without worrying that an ABS software update will stomp on them.
If you want to know more about the procedures that I use to do maintenance on ABS, let me know.
Cheers,
Robert
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО10-03-2007 03:40 AM
тАО10-03-2007 03:40 AM
Re: ABS_CATLG_00001 process
I'm using ABS V4.4(901). The help text on catalog configuration claims that STAGING is not even used on DISK type catalogs since no information about individual files is stored in these catalogs.
You might want to go through all of your catalogs and look at the settings to make sure that they are all the types you think they are(or not).
Also, have you ever done any tuning of your catalogs? If not, you could be having excessive IO activity because they need to be tuned.
This is an area that I've never been impressed with the out of the box tools they give you with ABS. If you want assistance with attempting a tune-up of all your catalogs I can try to help out with some DCL that you could adapt to your environment.
Robert
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО10-03-2007 07:49 AM
тАО10-03-2007 07:49 AM
Re: ABS_CATLG_00001 process
I think my problem is that I have 1 save request that's still using the default catalog of abs_catalog, which is of type files. I think I can either tune the abs_catalog catalog, or switch that backup to use my sray_catalog catalogk, which is of type disk.
I'd be interested in your tuning procedures if you don't mind sending them to me at trace.trembath@shell.com
Thanks!
Regards,
Trace
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО10-04-2007 03:29 AM
тАО10-04-2007 03:29 AM
Re: ABS_CATLG_00001 process
If you don't want to do specific file restores for these disks then it should use a DISKS type catalog. Otherwise I would assign the SAVE/ARCHIVE to a newly created FILES type catalog.
I've seen a couple of cases where the default ABS catalog files were 50GB+ in size without a CONVERT done for a long time. That has some performance impact on inserts but also on the ABS Catalog Cleanup job.
I always setup our devo cluster SAVEs with individual ARCHIVEs and catalogs - all starting with the same name for easy recognition.
That makes the catalogs (size) more manageable for regular CONVERTs and the catalog cleanup runs faster. I did no other tuning because catalog performance was acceptable with this setup.
/Guenther
- « Previous
-
- 1
- 2
- Next »