PSM Error -88017
Posted in 2023
Mark Scranton got Error -88017 invalid pool from PSM commands although backups worked. Art Kagel asked whether the paths existed and suggested creating a pool for the reported path. Mark found he had put full file paths in PSM_DBS_POOL and PSM_LOG_POOL, and the pool name appeared truncated. Changing the values to proper pool names was the implied fix.
Auto-generated by Claude from the posts below — may be imperfect; read the full thread.
Topics: Backup & Restore
Have been playing PSM lately and regardless of how many times I recreated the catalogs, redo (delete/add) devices and pools, etc. I continue to get the following error: 2023-12-13 09:34:18 25493912 21037456 The PSM is ready. 2023-12-13 09:34:18 25493912 21037456 Error -88017: Invalid pool /x001/PSM/this_engine/ specified 2023-12-13 09:34:18 25493912 21037456 Informix Primary Storage Manager session 100 opened. 2023-12-13 09:34:18.363653 25493912 21037456 Successfully connected to Storage Manager. I've re-init'd the catalogs, verified that path exists, etc. Interesting that PSM DOES work regardless. The message is more curiousity and it adds lots of chatter to the bar_act log (I have bar_act and psm_bar_act combined). Will also throw off log sniffers looking for -i error msgs. Here's the current topo: box:/here [some_engine:32] >onpsm -D list Error -88017: Invalid pool /x001/PSM/this_engine/ specified Informix Primary Storage Manager Device List Type Prio Block/Size (MB) Pool Name Device Name FILE HIGH --/-- DBSPOOL /x001/PSM/this_engine/DBSPOOL FILE HIGH --/-- LOGPOOL /x001/PSM/this_engine/LOGPOOL box:/here/ [some_engine:32] >onpsm -P list Error -88017: Invalid pool /x001/PSM/this_engine/ specified Informix Primary Storage Manager Pool List Pool Id Name 1 DBSPOOL 2 LOGPOOL 3 EXTPOOL ------------------------------ Thanks! Mark Scranton The Mark Scranton Group mark@markscranton.com ------------------------------
You know me Mark, I have to ask the "dumb" questions first: Do the paths /x001/PSM/this_engine/DBSPOOL & /x001/PSM/this_engine/LOGPOOL exist? Art ------------------------------ Art S. Kagel, President and Principal Consultant ASK Database Management Corp. www.askdbmgt.com ------------------------------
Yup. Checked perms while I was there, although I see an fun error msg if perms are bad "Exceeding available resources" or similar. I'm getting this Error -88017 on two different engines, but the backup/restore via PSM does work. I think I'll zero the engines and start fresh. Really would like to know where the error'ing path is stored. It's not in the catalogs since I've init'd (onpsm -C init) them a few times. Even grep'd for the string against the .dat and .idx files but no... I haven't perused sysutils completely. Thanks Art! box:/here/TMSG_HOME [some_engine:32] >ls -al /x001/PSM/this_engine/ total 8 drwxrwxr-x 2 informix informix 4096 Dec 13 09:02 catalogs drwxrwxr-x 3 informix informix 256 Dec 13 09:04 DBSPOOL drwxrwxr-x 3 informix informix 256 Dec 13 09:06 LOGPOOL ------------------------------ Thanks! Mark Scranton The Mark Scranton Group mark@markscranton.com ------------------------------
Curious. What's the servername? ------------------------------ Art S. Kagel, President and Principal Consultant ASK Database Management Corp. www.askdbmgt.com ------------------------------
Just for S's & G's, try creating a lower priority pool named just " /x001/PSM/this_engine/" and see what happens, 'cause that's the pool it is looking for. Don't know why though. ------------------------------ Art S. Kagel, President and Principal Consultant ASK Database Management Corp. www.askdbmgt.com ------------------------------
Silly me ... had the full file path of the pool in the PSM_DBS_POOL and PSM_LOG_POOL config params. Apparently there's some truncation going on with that parameter valkue. Would be curious where it is, etc. and the length. I added a new pool just to play and it appeared that it's name was truncated. Didn't dig further yet. Thanks for the help! Mark ------------------------------ Thanks! Mark Scranton The Mark Scranton Group mark@markscranton.com ------------------------------