From Hash file to loading Table
Moderators: chulett, rschirm, roy
From Hash file to loading Table
Hi,
i am storing the snapshot_date in the Hash file and if matches i am getting the snapshot_date but i am getting error ORA-01841: (full) year must be between -4713 and +9999, and not be 0. The same hash file working good in another job but i am getting error in one job. So what should i do shall i had to convert into internal date format and then convert into the orginal oracle date and pass to the target.
Thanks
sri
i am storing the snapshot_date in the Hash file and if matches i am getting the snapshot_date but i am getting error ORA-01841: (full) year must be between -4713 and +9999, and not be 0. The same hash file working good in another job but i am getting error in one job. So what should i do shall i had to convert into internal date format and then convert into the orginal oracle date and pass to the target.
Thanks
sri
More information needed.
* What format is the date stored in in the hashed file?
* What format is it in when you send it to Oracle?
* How is it defined in your target - DATE? TIMESTAMP?
* What datatype did you define it as in your job - Date? Timestamp? Varchar? What size?
* What kind of transformations are you doing on it now? Anything?
Not saying this is an all inclusive set of questions, but just trying to give you an idea that more information is needed to do anything other than guess at what you are doing and what an appropriate solution would be. And I'd rather see too much information rather than too little.
![Confused :?](./images/smilies/icon_confused.gif)
* What format is the date stored in in the hashed file?
* What format is it in when you send it to Oracle?
* How is it defined in your target - DATE? TIMESTAMP?
* What datatype did you define it as in your job - Date? Timestamp? Varchar? What size?
* What kind of transformations are you doing on it now? Anything?
Not saying this is an all inclusive set of questions, but just trying to give you an idea that more information is needed to do anything other than guess at what you are doing and what an appropriate solution would be. And I'd rather see too much information rather than too little.
-craig
"You can never have too many knives" -- Logan Nine Fingers
"You can never have too many knives" -- Logan Nine Fingers
additional information about the question
The date in the hash file is stored in the Timestamp format and i am getting the timestamp format as it is and storing in the oracle table in timestamp format
Thanks
sri
Thanks
sri
So, is the target an Oracle DATE field? If you treat this as a Timestamp in the job and make sure it looks like YYYY-MM-DD HH24:MI:SS when it gets to Oracle, you should be fine. This also assumes you are using an OCI stage to write to the database, that or the DRS stage set to Oracle.
-craig
"You can never have too many knives" -- Logan Nine Fingers
"You can never have too many knives" -- Logan Nine Fingers
-
- Participant
- Posts: 3337
- Joined: Mon Jan 17, 2005 4:49 am
- Location: United Kingdom
-
- Participant
- Posts: 54607
- Joined: Wed Oct 23, 2002 10:52 pm
- Location: Sydney, Australia
- Contact:
-
- Participant
- Posts: 54607
- Joined: Wed Oct 23, 2002 10:52 pm
- Location: Sydney, Australia
- Contact:
Ok. I get those at times using 7.0.1, typically when I've use a connection for multiple things before trying to debug a job. Usually can be 'worked around' by opening a new Designer session and doing the debugging of the job in isolation.
-craig
"You can never have too many knives" -- Logan Nine Fingers
"You can never have too many knives" -- Logan Nine Fingers
-
- Participant
- Posts: 54607
- Joined: Wed Oct 23, 2002 10:52 pm
- Location: Sydney, Australia
- Contact: