ERP Associates, Inc.

Don’t you just love production support?  There’s nothing like waking up in the morning, finishing your coffee, and not having a flippin’ clue what’s about to happen.

It’s been another one of those days, so I thought I’d share some of the problems I’ve looked at and their solutions.

Issue#1: Nvision Drilldown throws error "Error occurred during initialization of VM Could not reserve enough space for object heap"

Solution #1: This turned out to be related to some patches that were applied to our PSNT server over the weekend.  Our NT admin identified a hotfix and is in the process of applying it.

Issue#2: Need to delete reports from the report repository because they contain bad results.

Solution #2: Ran the following SQL to expire the reports.  Then I plan to follow up and run the PRCSSYSPURGE process to get rid of ‘em for good.

update ps_cdm_list
set expiration_date = trunc(sysdate)-7
where prcsinstance = '1368545'
/

update PSRF_RINFO_TBL
set expiration_date = sysdate-7
where PSRF_REPORT_ID in (select PSRF_REPORT_ID from PSRF_RINFO_TBL where prcsinstance = '1368545')
/

Issue #3: Integration Broker domain is inactive, and everything is disabled on the "Domain Status" component.  This was a non-production environment and it hasn’t been used in a while.

Solution #3: After double-checking security (it’s all good) and making sure the pub/sub processes were configured on the app server (check), I discovered that failover was enabled but wasn’t set up appropriately.  After unchecking "Enable failover", saving, and going back to the Domain Status page I was able to purge domain status and set all domains to active.

Issue #4: User can’t log on using Canadian French language.  System throws this error:  "Connection failed because the selected language is not active in the database."  Once again this is a non-prod environment.

Solution#4:  Checked "Canadian French" in Manage Installed Languages component. Navigation is PeopleTools > Utilities > International > Languages.

Issue #5: Just discovered that custom text translations didn’t upgrade from the old W3EB_TEXT_LANG table.

Resolution #5: Ran the following SQL to fix it:

insert into PS_HR_SSTEXT_LANG
select 'HEB', ' ', text_id, effdt, benefit_program, plan_type,event_class, ' ', language_cd, w3eb_text  from PS_W3EB_TEXT_LANG a where language_cd = 'CFR' and not exists (select 'x' from PS_HR_SSTEXT_LANG where text_id = a.text_id and language_cd = a.language_cd)

I think I'll call it a day.