Highlighted
Respected Contributor.. Respected Contributor..
Respected Contributor..
406 views

i cant show shedules after updating pg_ident

Jump to solution

Hi all,

I have an issue an idb when i tried to start. I solve problem adding to "System"   user name in pg_ident.conf file.

After that, scheduled jobs not triggered own by own & in home screen under the scheduler tab, cant show to scheduled jobs.

clipboard_image_0.png

clipboard_image_2.png

clipboard_image_3.png

0 Likes
1 Solution

Accepted Solutions
Micro Focus Expert
Micro Focus Expert

Re: i cant show shedules after updating pg_ident

Jump to solution

Hello @mtduran

This error:

2019-09-25 03:00:00 MDT ERROR: duplicate key value violates unique constraint "unique_schedule_id_start_time"

Looks like a known issue. There is a workaround: 

1. stop DP services
2. Open "webservice.properties" file in folder

on WIN: ProgramData\OmniBack\Config\client\components\jce-dispatcher

3. Add following line:

jce-dispatcher.executionmanager.priorityjob.skipabr = true

4. remove all debug files from AppServer folder:

on WIN: \ProgramData\OmniBack\log\AppServer\

5. start DP services

If error still persist, exist a possible hotfix: QCCR2A77330

Regards, 

 

Andres Fallas Salazar
Customer Support Engineer

If you find that this or any other post resolves your issue, please be sure to mark it as an accepted solution.
If you are satisfied with anyone’s response please remember to give them a LIKE by clicking on the bottom at the left of the post and show your appreciation.

View solution in original post

5 Replies
Highlighted
Micro Focus Expert
Micro Focus Expert

Re: i cant show shedules after updating pg_ident

Jump to solution

Hello @mtduran

The line added is not correct. Should be like this: 

hpdpidb        SYSTEM        hpdp

After correct it, restart the services. 

Check again. 

Anyways, I am thinking that these errors are not related, at least not directly. What is your DP version? Do you see any pop-up in the Home context when you open it? Check the server.log (ProgramData\Omniback\log\AppServer) for ERROR or FATAL. 

Regards, 

Andres Fallas Salazar
Customer Support Engineer

If you find that this or any other post resolves your issue, please be sure to mark it as an accepted solution.
If you are satisfied with anyone’s response please remember to give them a LIKE by clicking on the bottom at the left of the post and show your appreciation.
0 Likes
Highlighted
Respected Contributor.. Respected Contributor..
Respected Contributor..

Re: i cant show shedules after updating pg_ident

Jump to solution

Hello @Victor_F_DP 

I am using A 10.02 ver.

First time i was using "SYSTEM" after that i changed.

Below popups shown in screen.

clipboard_image_0.png

clipboard_image_1.png

 

I find below path some fatal & errors.

C:\ProgramData\OmniBack\server\db80\pg\pg_log

 

2019-09-25 03:00:00 MDT ERROR: duplicate key value violates unique constraint "unique_schedule_id_start_time"
2019-09-25 03:00:00 MDT DETAIL: Key (schedule_id, start_time)=(af3acfc1-f13e-48a6-89e2-f1e9f017408d, 1569628800000) already exists.
2019-09-25 03:00:00 MDT STATEMENT: insert into jce_schedule_triggers (end_time, excluded_instances, job_id, job_seq_id, schedule_id, schedule_seq_id, start_time, id) values ($1, $2, $3, $4, $5, $6, $7, $8)
2019-09-25 03:00:01 MDT ERROR: duplicate key value violates unique constraint "unique_schedule_id_start_time"
2019-09-25 03:00:01 MDT DETAIL: Key (schedule_id, start_time)=(c0bfc775-1121-440a-b40a-827e6bbf0a0a, 1569747600000) already exists.
2019-09-25 03:00:01 MDT STATEMENT: insert into jce_schedule_triggers (end_time, excluded_instances, job_id, job_seq_id, schedule_id, schedule_seq_id, start_time, id) values ($1, $2, $3, $4, $5, $6, $7, $8)
2019-09-25 03:00:01 MDT ERROR: duplicate key value violates unique constraint "unique_schedule_id_start_time"
2019-09-25 03:00:01 MDT DETAIL: Key (schedule_id, start_time)=(6ba55561-f6e5-4cf9-b866-28803078e0db, 1569646800000) already exists.
2019-09-25 03:00:01 MDT STATEMENT: insert into jce_schedule_triggers (end_time, excluded_instances, job_id, job_seq_id, schedule_id, schedule_seq_id, start_time, id) values ($1, $2, $3, $4, $5, $6, $7, $8)
2019-09-25 03:00:01 MDT ERROR: duplicate key value violates unique constraint "unique_schedule_id_start_time"
2019-09-25 03:00:01 MDT DETAIL: Key (schedule_id, start_time)=(fd63e917-73df-4f63-af1d-04c1b0c1a466, 1569891600000) already exists.
2019-09-25 03:00:01 MDT STATEMENT: insert into jce_schedule_triggers (end_time, excluded_instances, job_id, job_seq_id, schedule_id, schedule_seq_id, start_time, id) values ($1, $2, $3, $4, $5, $6, $7, $8)
2019-09-25 03:00:01 MDT ERROR: duplicate key value violates unique constraint "unique_schedule_id_start_time"
2019-09-25 03:00:01 MDT DETAIL: Key (schedule_id, start_time)=(c96b9d2f-b22d-4bc7-992a-8fbddb0996b5, 1569398400000) already exists.
2019-09-25 03:00:01 MDT STATEMENT: insert into jce_schedule_triggers (end_time, excluded_instances, job_id, job_seq_id, schedule_id, schedule_seq_id, start_time, id) values ($1, $2, $3, $4, $5, $6, $7, $8)
2019-09-25 03:00:02 MDT ERROR: duplicate key value violates unique constraint "unique_schedule_id_start_time"
2019-09-25 03:00:02 MDT DETAIL: Key (schedule_id, start_time)=(b1fee9d0-3a60-42f4-9eb5-c4ea096697b7, 1569747600000) already exists.
2019-09-25 03:00:02 MDT STATEMENT: insert into jce_schedule_triggers (end_time, excluded_instances, job_id, job_seq_id, schedule_id, schedule_seq_id, start_time, id) values ($1, $2, $3, $4, $5, $6, $7, $8)
2019-09-25 06:02:12 MDT LOG: no match in usermap "hpdpidb" for user "hpdp" authenticated as "SYSTEM"
2019-09-25 06:02:12 MDT FATAL: SSPI authentication failed for user "hpdp"
2019-09-25 06:05:49 MDT LOG: received fast shutdown request
2019-09-25 06:05:49 MDT LOG: aborting any active transactions
2019-09-25 06:05:49 MDT FATAL: terminating connection due to administrator command
2019-09-25 06:05:49 MDT FATAL: terminating connection due to administrator command
2019-09-25 06:05:49 MDT FATAL: terminating connection due to administrator command
2019-09-25 06:05:49 MDT FATAL: terminating connection due to administrator command
2019-09-25 06:05:49 MDT FATAL: terminating connection due to administrator command
2019-09-25 06:05:49 MDT FATAL: terminating connection due to administrator command
2019-09-25 06:05:49 MDT FATAL: terminating connection due to administrator command
2019-09-25 06:05:49 MDT FATAL: terminating connection due to administrator command
2019-09-25 06:05:49 MDT FATAL: terminating connection due to administrator command
2019-09-25 06:05:49 MDT FATAL: terminating connection due to administrator command
2019-09-25 06:05:49 MDT FATAL: terminating connection due to administrator command
2019-09-25 06:05:49 MDT FATAL: terminating connection due to administrator command
2019-09-25 06:05:49 MDT FATAL: terminating connection due to administrator command
2019-09-25 06:05:49 MDT FATAL: terminating connection due to administrator command
2019-09-25 06:05:49 MDT FATAL: terminating connection due to administrator command
2019-09-25 06:05:49 MDT FATAL: terminating connection due to administrator command
2019-09-25 06:05:49 MDT FATAL: terminating connection due to administrator command
2019-09-25 06:05:49 MDT FATAL: terminating connection due to administrator command
2019-09-25 06:05:49 MDT FATAL: terminating connection due to administrator command
2019-09-25 06:05:49 MDT FATAL: terminating connection due to administrator command
2019-09-25 06:05:49 MDT FATAL: terminating connection due to administrator command
2019-09-25 06:05:49 MDT FATAL: terminating connection due to administrator command

 

From server log i cant see ant error but to many warnings shown.

C:\ProgramData\OmniBack\log\AppServer

 

2019-09-26 23:59:49,889 WARN [com.hp.im.jce.serviceregistry.ServiceRegistrationHandler] (Timer-10) Failed to register service ServiceDescription [id=null, name=dp-licenseprovider, version=1.1.0, properties=null, url=MYBACKUPSERVER expiresAt=null]: java.lang.NullPointerException
2019-09-26 23:59:51,425 WARN [com.hp.im.jce.serviceregistry.ServiceRegistrationHandler] (Timer-3) Failed to register service ServiceDescription [id=null, name=jce-jobexecutionengine, version=1.1.0, properties={SupportedJobType=EXECUTE_DP_COPY}, url=MYBACKUPSERVER expiresAt=null]: java.lang.NullPointerException
2019-09-26 23:59:51,908 WARN [com.hp.im.jce.serviceregistry.ServiceRegistrationHandler] (Timer-6) Failed to register service ServiceDescription [id=null, name=jce-jobexecutionengine, version=1.1.0, properties={SupportedJobType=EXECUTE_DP_MEDIACOPY}, url=MYBACKUPSERVERexpiresAt=null]: java.lang.NullPointerException
2019-09-26 23:59:52,585 WARN [com.hp.im.jce.serviceregistry.ServiceRegistrationHandler] (Timer-7) Failed to register service ServiceDescription [id=null, name=jce-jobexecutionengine, version=1.1.0, properties={SupportedJobType=EXECUTE_DP_BACKUP}, url=MYBACKUPSERVER expiresAt=null]: java.lang.NullPointerException
2019-09-26 23:59:52,887 WARN [com.hp.im.jce.serviceregistry.ServiceRegistrationHandler] (Timer-5) Failed to register service ServiceDescription [id=null, name=jce-jobexecutionengine, version=1.1.0, properties={SupportedJobType=EXECUTE_DP_CONSOLIDATION}, url=MYBACKUPSERVER expiresAt=null]: java.lang.NullPointerException
2019-09-26 23:59:53,707 WARN [com.hp.im.jce.serviceregistry.ServiceRegistrationHandler] (Timer-4) Failed to register service ServiceDescription [id=null, name=jce-jobexecutionengine, version=1.1.0, properties={SupportedJobType=EXECUTE_DP_REPORTING}, url=MYBACKUPSERVER expiresAt=null]: java.lang.NullPointerException
2019-09-26 23:59:53,794 WARN [com.hp.im.jce.serviceregistry.ServiceRegistrationHandler] (Timer-9) Failed to register service ServiceDescription [id=null, name=jce-jobexecutionengine, version=1.1.0, properties={SupportedJobType=EXECUTE_DP_VERIFICATION}, url=MYBACKUPSERVER, expiresAt=null]: java.lang.NullPointerException
2019-09-26 23:59:53,966 INFO [com.hp.autopassj.core.config.ConfigurationManager] (Thread-151) [com.hp.autopassj.core.config.ConfigurationManager : Inside ConfigurationManeger getLicenseStore] :: Inside getLicenseStorecom.hp.autopassj.core.license.LicenseStore@3e113ab0
2019-09-26 23:59:56,583 WARN [com.hp.im.jce.serviceregistry.ServiceRegistrationHandler] (Timer-11) Failed to register service ServiceDescription [id=null, name=dp-loginprovider, version=1.1.0, properties=null, url=MYBACKUPSERVER, expiresAt=null]: java.lang.NullPointerException

0 Likes
Micro Focus Expert
Micro Focus Expert

Re: i cant show shedules after updating pg_ident

Jump to solution

Hello @mtduran

This error:

2019-09-25 03:00:00 MDT ERROR: duplicate key value violates unique constraint "unique_schedule_id_start_time"

Looks like a known issue. There is a workaround: 

1. stop DP services
2. Open "webservice.properties" file in folder

on WIN: ProgramData\OmniBack\Config\client\components\jce-dispatcher

3. Add following line:

jce-dispatcher.executionmanager.priorityjob.skipabr = true

4. remove all debug files from AppServer folder:

on WIN: \ProgramData\OmniBack\log\AppServer\

5. start DP services

If error still persist, exist a possible hotfix: QCCR2A77330

Regards, 

 

Andres Fallas Salazar
Customer Support Engineer

If you find that this or any other post resolves your issue, please be sure to mark it as an accepted solution.
If you are satisfied with anyone’s response please remember to give them a LIKE by clicking on the bottom at the left of the post and show your appreciation.

View solution in original post

Highlighted
Respected Contributor.. Respected Contributor..
Respected Contributor..

Re: i cant show shedules after updating pg_ident

Jump to solution

Thanks @Victor_F_DP 

Without to hotfix my problem solved.

Best Regards.

 

 

Highlighted
Micro Focus Expert
Micro Focus Expert

Re: i cant show shedules after updating pg_ident

Jump to solution

Hello @mtduran,

I'm glad this is working now. This problem is also fixed in later versions of Data Protector (A.10.03 and later).

Regards,
Sebastian Koehler

---
Please use the Like button below, if you find this post useful.
0 Likes
The opinions expressed above are the personal opinions of the authors, not of Micro Focus. By using this site, you accept the Terms of Use and Rules of Participation. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.) and Hewlett Packard Enterprise Company. As of September 1, 2017, the Material is now offered by Micro Focus, a separately owned and operated company. Any reference to the HP and Hewlett Packard Enterprise/HPE marks is historical in nature, and the HP and Hewlett Packard Enterprise/HPE marks are the property of their respective owners.