Getting Bad Attribute Name WHILE Running Custom JOB

Bablu

Hi ALL,

While running my custom job it is working fine till Saturday but now it is not working it get failed sand says

[DM_API_E_BADATTRNAME]error: "Bad attribute name 'timestamp' for document/object' null

Please Suggest me how to trouble shoot the error.

Please point it as i am stuck about past 1 week. Production is down.

Thanks

Bablu

Find more posts tagged with

Note:

If there are Accepted Answers, those will be shown by default. You can switch to 'All Replies' by selecting the tab below.

Accepted answers

Gane

Hi Bablu

This error is because of attribute "timestamp" not available for that object type.

Check whether the object created for the correct object type that has this attribute "timestamp" if setting via java.

All comments

Andre Machado

Could you check the queries in your custom job?

I think that the correct attribute name may be "time_stamp".

Bablu

Hi AmmaChand,

Thanks for your response but attribute is same "timestamp" not "time_stamp".

same job it was running last week but this week it is getting failed. I have clear the cache and republish the object_type from API command. It is not Working . Please provide me some input to resolve this issue.

Thanks

Bablu

Gane

Hi Bablu

This error is because of attribute "timestamp" not available for that object type.

Check whether the object created for the correct object type that has this attribute "timestamp" if setting via java.

Bablu

Hi Ammchand,

Thank you for your reply. Issue has been resolved as in /Temp folder there was an Document which is belong to some other object_type with no timestamp attribute. We are iterating all the document in temp folder,there it caught. After printing the r_object_id we found it and checked the attribute available.Finally we move that document to other location and now it is Working fine. Thanks You Very Much AMMCHAND. Cheers!!!!!

Thanks

Bablu Gupta