nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

unable to data deploy date

System

Hi,

I am facing a problem for which i am not able to think of a resolution.
I am trying to deploy two dates onto the Database. Both the dates have same format, but only one of them (Creation Date) is converted to the proper date format... No matter what the sequence is only CREATION_DATE is being deployed. The config file had the following two lines.

column name="MODIFIED_DATE" data-type="DATE" data-format="dd-MM-yyyy HH:mm" db-datetime-format="dd-MM-yyyy HH:mm" value-from-field="TeamSite/Metadata/modified_date" allows-null="yes"/

column name="CREATION_DATE" data-type="DATE" data-format="dd-MM-yyyy HH:mm" db-datetime-format="dd-MM-yyyy HH:mm" value-from-field="TeamSite/Metadata/creation_date" allows-null="yes"/

-------------------------------------------------------------------
LOG
--------------------------------------------------------------------
DBD: Column: MODIFIED_DATE, field: TeamSite/Metadata/modified_date, Index: 5,Converting '...........' to LONGVARCHAR
DBD: Column: CREATION_DATE, field: TeamSite/Metadata/creation_date, Index: 6,Converting '08-07-2006 12:33' to TIMESTAMP

DBD: *******************************************************
DBD: SQLException occured in TDbSchemaGroupCfg
DBD: Exception Message: ORA-01843: not a valid month

DBD: Vendor Error Code: 1843
DBD: SQL state: 22008
DBD: *******************************************************
Regards
Dixit
TS 6.5 SP2 | OpenDeploy Version: 6.0.2.1.0

Find more posts tagged with

Comments

kaalraa

Dixit,

Have you checked the Modified_Date with different values and is it giving the same error log with each example?

Also please provide info about the values.. which you have tested. Also try to put the same date as well as format for both the fields.

Hi,

I am facing a problem for which i am not able to think of a resolution.
I am trying to deploy two dates onto the Database. Both the dates have same format, but only one of them (Creation Date) is converted to the proper date format... No matter what the sequence is only CREATION_DATE is being deployed. The config file had the following two lines.

column name="MODIFIED_DATE" data-type="DATE" data-format="dd-MM-yyyy HH:mm" db-datetime-format="dd-MM-yyyy HH:mm" value-from-field="TeamSite/Metadata/modified_date" allows-null="yes"/

column name="CREATION_DATE" data-type="DATE" data-format="dd-MM-yyyy HH:mm" db-datetime-format="dd-MM-yyyy HH:mm" value-from-field="TeamSite/Metadata/creation_date" allows-null="yes"/

-------------------------------------------------------------------
LOG
--------------------------------------------------------------------
DBD: Column: MODIFIED_DATE, field: TeamSite/Metadata/modified_date, Index: 5,Converting '...........' to LONGVARCHAR
DBD: Column: CREATION_DATE, field: TeamSite/Metadata/creation_date, Index: 6,Converting '08-07-2006 12:33' to TIMESTAMP

DBD: *******************************************************
DBD: SQLException occured in TDbSchemaGroupCfg
DBD: Exception Message: ORA-01843: not a valid month

DBD: Vendor Error Code: 1843
DBD: SQL state: 22008
DBD: *******************************************************
Regards
Dixit
TS 6.5 SP2 | OpenDeploy Version: 6.0.2.1.0

Migrateduser

Have tried everything... even gave same value-from-field even then,it does not work!!

-Dixit

kaalraa

Have tried everything... even gave same value-from-field even then,it does not work!!

-Dixit

Better get a Kingsize puff... sometimes micro things are not visible using microscopic eyes as well. Smiley Very Happy

Migrateduser

What does your DCR look like? It's curious that DD is

trying to convert your DATE field into LONGVARCHAR.

Dave

Riepilogo-65.pdf

Migrateduser

What does your DCR look like? It's curious that DD is
trying to convert your DATE field into LONGVARCHAR.

Dave

Dave,

The DCR is in IWOV format,,
but here we are deploying the METADATA of the generated HTMLs.
If you can throw more light on this, that would be great, even i am taken by surprise to see that kind of error...

Only one of the fields gets converted to the TIMESTAMP, even if the values are picked up from same metadata value... and the problem seems to be only with the MODIFIED_DATE. I put any permutation and combination of the sequence within the db-schema problem seems to be MODIFIED_DATE...

Thanks
Dixit

Migrateduser

Okay -- in that case, what does your datacapture.cfg look like? I understand that the values are the same but I'm interested in knowing how these two columns originate.

Dave

Migrateduser

Okay -- in that case, what does your datacapture.cfg look like? I understand that the values are the same but I'm interested in knowing how these two columns originate.

Dave

These values does not come from the DCR, i am setting the values in the presentation template.

using iwextattr -s '/TeamSite/Metadata/creation_date' and iwextattr -s '/TeamSite/Metadata/modified_date'

The datacapture.cfg does not get involved here.

-dixit

Migrateduser

Apparently, I've been misunderstanding you but you cleared it up (at least a bit). At first, I thought you were doing it through the DCT. Then, when you said you were deploying metadata, I thought you were doing it through Metadata Capture. I understand from your last message that you're not doing it this way.

That's fine but can you post your *entire* DD definition so others and myself can get some context?

Migrateduser

Dave,

Please find the attached dd config....

I have included the DD config that is creating probs.

along with the concerned deployment there is another deployment which i haven't included, that takes care of the DCR field deployments and is working fine .

Thanks
Dixit

kaalraa

Dixit,

Just check your code once ... i have gone thru and it is saying creation_date for both the fields; creation_date as well as modified_date.

{column name="MODIFIED_DATE" data-type="DATE" data-format="dd-MM-yyyy HH:mm" db-datetime-format="dd-MM-yyyy HH:mm" value-from-field="TeamSite/Metadata/creation_date" allows-null="yes"/}

{column name="CREATION_DATE" data-type="DATE" data-format="dd-MM-yyyy HH:mm" db-datetime-format="dd-MM-yyyy HH:mm" value-from-field="TeamSite/Metadata/creation_date" allows-null="yes"/}

Migrateduser

Yes, at first i was putting different fields, but it was not working, so i Put same metadata value in both to check, if the config works, but it does not,,, :-(

-dixit

rohitspathak123

Hi

I am also running into same issue. Did you got the answer for it.

Its very URGENT.

Rohit