ORA-01861: literal string does not match format..

[bgallesio]

Hello, I get this error when check Out a package.



OraOleDB
ORA-01861: literal does not match format string.

Any comment?
TIA.

-----
Oracle9i Release 9.2.0.8.0 - 64bit Production
EA 6.5.805 (build 805)
Database Version: 4.01

[«Midnight»]

I have not seen this one before, but it could be version-related.

The big question is where the problem originates. Is it something with the DBMS or is it from your version control software. What VC are you using?

A quick guess is to verify that you don't have a problem with stored credentials. If one of the products has trashed a username or password, you could run into problems.

A while back some users reported problems with older Oracle client versions. Unfortunately I cannot remember whether this was before build 805 or not. You might want to try 806 - if memory serves that was the final 6.5 release - or at least read the release notes. You can find the release notes in the Latest News section of the forum, or on the History page of the Sparx site: http://www.sparxsystems.com/products/ea_history.html

I had some problems around that time with SQL Server. They were kind of strange, but involved mysterious problems trying to connect. I eventually downloaded the SQL scripts from the Sparx site - even though I thought mine were up to date - and recreated my repository schemas. Problems went away... [Unfortunately, version 4.01 has been the reported version number for years, so this is difficult to track.]

I suggest you send an immediate support request to Sparx. This might not be a bug report, since you are almost a year behind the production software release. There is a link on the Registered Users page that points here: http://www.sparxsystems.com/registered/reg_support.html. Remember to include information about your version control product.

David

[bgallesio]

Thanks David.

Version control is Microsoft Visual SourceSafe 6.0b (Build 9848)... an oldies.

For the moment, I changed the date and time format client "HH: MI: SS" from "H:MI:SS TT" and is working.

[«Midnight»]

...
For the moment, I changed the date and time format client "HH: MI: SS" from "H:MI:SS TT" and is working...

Well, that's the main thing.

Still, this is the kind of surprise you don't need.

Were you setting VC or the DBMS up for the first time, or did this just come out of the blue? In the former case I suggest you verify that this format is documented, and send in a bug report if it is not. In the latter case definitely send in a bug report (not a support request). Sparx will want to guard against this happening at random.

You'll find the correct form by clicking the Report a Bug link below the Support link near the bottom of any forum page. If you are a registered user, you should then click the appropriate link above the form on the next page. If not, then fill out the form and send it in.

If you do send a bug report, please post back to this thread if Sparx has anything to say on the subject. This will let the rest of the community know what's going on.

David

[Eve]

It's a database error, so it's unlikely to be related to version control.  If you imported your XMI file without version control it would still probably come up.

I suspect that this is related to the Oracle DB and that it is likely that it has been fixed in a more recent build.

To that end, I would strongly recommend downloading build 818 and trying under that.  (Use the beta at your own risk as it is for non-production environments and models.)

[«Midnight»]

I agree with Simon but...

I noted that you are using EA 6.5, which is why I mentioned build 806. The correction is likely in 818, but I do not know if it was first seen before then.

Is your organization - or are you - expecting to upgrade to EA 7.0 at this time?

If not, is it worth considering the upgrade to solve this problem?

The above are questions that nobody can answer for you. All we can do is expose the issue so you can consider it in light of your circumstances.

David