Re: Move sysadmin database

Posted in 2016

BENJAMIN THOMPSON — Thu, 18 Aug 2016 14:05:15 — source: IIUG Forums & Mailing Lists

Frank, Sorry to reply to such an old post but I am seeing this same error intermittently when building instances in fully automated environments with 11.70.FC7W1. I agree that the problem is not a lack of space in the target dbspace or any other parameter because the problem is random and occurs in some runs and not others, with identical parameters. Did you ever find a solution? If not I may raise a PMR. Ben.

↪ replying to BENJAMIN THOMPSON

FRANK — Wed, 31 Aug 2016 15:42:22 — source: IIUG Forums & Mailing Lists

Ben, We eventually moved. It seems the solution was, we could not run the task with dbaccess in interactive mode, instead, run it in a batch mode ( command line , something like, dbaccess sysadmin move_sysadmin.sql ), EXECUTE FUNCTION task("reset sysadmin","dbdw00"); You should see online log, 15:35:07 SCHAPI: thread dbWorker2 task Low Memory Reconfig(45-7422) shutting down 15:35:07 SCHAPI: thread dbWorker1 task mon_chunk(6-7423) shutting down 15:35:08 SCHAPI: thread dbScheduler(94) shutting down 15:35:17 SCHAPI: 'sysadmin' database will be moved to 'dbdata00'. See online message log. 15:35:17 Building 'sysadmin' database ... 15:35:19 Logical Log 190095 Complete, timestamp: 0x974e1998. 15:35:20 'sysadmin' database built successfully. 15:35:20 SCHAPI: Started dbScheduler thread. 15:35:20 Auto Registration is synced 15:35:20 Updating Low Memory Manager to version 11 15:35:20 Installing patch to upgrade ph_task code. version(13.04) 15:35:20 SCHAPI: Started 2 dbWorker threads. 15:35:20 Checkpoint Completed: duration was 0 seconds. 15:35:20 Wed Aug 31 - loguniq 190096, logpos 0xa19018, timestamp: 0x974e83f4 Interval: 500069 Thanks Frank On Thu, Aug 18, 2016 at 10:05 AM, BENJAMIN THOMPSON < benjamin.thompson@skybettingandgaming.com> wrote: > Frank, > > Sorry to reply to such an old post but I am seeing this same error > intermittently when building instances in fully automated environments with > 11.70.FC7W1. > > I agree that the problem is not a lack of space in the target dbspace or > any > other parameter because the problem is random and occurs in some runs and > not > others, with identical parameters. > > Did you ever find a solution? If not I may raise a PMR. > > Ben. > > > ************************************************************ > ******************* > Forum Note: Use "Reply" to post a response in the discussion forum. > > --001a1134fa3e2645e6053b5ff104

↪ replying to FRANK

Jack Parker — Wed, 31 Aug 2016 15:55:11 — source: IIUG Forums & Mailing Lists

I've found that the move doesn't happen as long as the database is open. So issue the command in interactive mode, then close the DB - or exit dbaccess. j. On 8/31/16 11:42 AM, FRANK wrote: > Ben, > > We eventually moved. > It seems the solution was, we could not run the task with dbaccess in > interactive mode, instead, run it in a batch mode ( command line , > something like, dbaccess sysadmin move_sysadmin.sql ), > > EXECUTE FUNCTION task("reset sysadmin","dbdw00");> > You should see online log, > > 15:35:07 SCHAPI: thread dbWorker2 task Low Memory Reconfig(45-7422) > shutting down > 15:35:07 SCHAPI: thread dbWorker1 task mon_chunk(6-7423) shutting down > 15:35:08 SCHAPI: thread dbScheduler(94) shutting down > 15:35:17 SCHAPI: 'sysadmin' database will be moved to 'dbdata00'. See > online message log. > 15:35:17 Building 'sysadmin' database ... > 15:35:19 Logical Log 190095 Complete, timestamp: 0x974e1998. > 15:35:20 'sysadmin' database built successfully. > 15:35:20 SCHAPI: Started dbScheduler thread. > 15:35:20 Auto Registration is synced > 15:35:20 Updating Low Memory Manager to version 11 > 15:35:20 Installing patch to upgrade ph_task code. version(13.04) > 15:35:20 SCHAPI: Started 2 dbWorker threads. > 15:35:20 Checkpoint Completed: duration was 0 seconds. > 15:35:20 Wed Aug 31 - loguniq 190096, logpos 0xa19018, timestamp: > 0x974e83f4 Interval: 500069 > > Thanks > Frank > > On Thu, Aug 18, 2016 at 10:05 AM, BENJAMIN THOMPSON < > benjamin.thompson@skybettingandgaming.com> wrote: > >> Frank, >> >> Sorry to reply to such an old post but I am seeing this same error >> intermittently when building instances in fully automated environments with >> 11.70.FC7W1. >> >> I agree that the problem is not a lack of space in the target dbspace or >> any >> other parameter because the problem is random and occurs in some runs and >> not >> others, with identical parameters. >> >> Did you ever find a solution? If not I may raise a PMR. >> >> Ben. >> >> >> ************************************************************ >> ******************* >> Forum Note: Use "Reply" to post a response in the discussion forum. >> >> > --001a1134fa3e2645e6053b5ff104 > > > ******************************************************************************* > Forum Note: Use "Reply" to post a response in the discussion forum. > >

Glossary

dbspace