Unable to Save New Journals in Hyperion Financial Management Target Application After the Application Database Tables Were Manually Copied
(Doc ID 1279004.1)
Last updated on AUGUST 18, 2022
Applies to:
Hyperion Financial Management - Version 11.1.1.3.00 and laterInformation in this document applies to any platform.
Symptoms
The application database tables have been manually copied from one Oracle database schema to another. However, when users attempt to save new journals, the journal doesn't get saved.
Additionally an error similar to the following is added to the HsvEventLog.log file:
<Num HEX=0x80040E2F>-2147217873</Num>
<Description Src=ADO>Value violated the integrity constraints for a
column or table.</Description>
<Type>1</Type>
<DTime>11/17/2010 12:39:01 PM</DTime>
<Svr>SERVER1</Svr>
<File>CHsvDSJournals.cpp</File>
<Line>2717</Line>
<Ver>11.1.1.3.0.2413</Ver>
<DStr>INSERT INTO APP1_JL_1_2010 (JOURNAL_ID, TYPE, STATUS,
ATTRIBUTE, JOURNAL_GROUP, DESCRIPTION, LABEL, UNIQUE_LABEL, PERIOD_ID,
VALUE_ID, SINGLE_ENTITY_ID, SINGLE_PARENT_ID, SECURITYCLASS_ID, CREATED_USER,
POSTED_USER, APPROVED_USER, CREATED_DATE_TIME, POSTED_DATE_TIME,
APPROVED_DATE_TIME) VALUES (APP1_JL_1_2010_SEQ.NextVal, 4, 2, 1,
N'ARINTRU', N'866_JR003387M_To reclass Head Office Cost to BG',
N'H3_ARINTRU_004', N'H3_ARINTRU_004', 83886082, 13, 62, -1, 99,
N'user1@Native Directory', N'', N'', 40499.5270949074, 0, 0)</DStr>
<ExErr></ExErr>
<Param>ORA-00001: unique constraint (HFM.SYS_C0046804)
violated</Param>
Changes
Cause
To view full details, sign in with your My Oracle Support account. |
|
Don't have a My Oracle Support account? Click to get started! |
In this Document
Symptoms |
Changes |
Cause |
Solution |