Solaris 8 hangs and data access error on reboot

Hi
using solaris 5.8 on UltraSPARC-IIi 360MHz.
I know it is an old hardware but similiar hardware is running fine. here is the issue,
System booted : works okay for some time then display was hung so system was rebooted ..it gave data access error. again rebooted and it came up fine..
I have pasted the /var/adm/messages here..
http://pastebin.com/m5d2d1d53
Is it a CPU problem or Hard disk or memory issue ? or something else ?
what could be solution , a kernel patch is an option ?
uname -a
SunOS sparc5 5.8 Generic_108528-07 sun4u sparc SUNW,Ultra-5_10
test-all at OBP did not show any error.. passed all.
Thanks

I cant see the /var/adm/messages output, Since you have already performed a Full Diagnostic check, then you boot your solaris using CD and then perform full FSCK on root File Systems and see any errors get reported. Keep doing fsck 2 -3 times untill all the errors are clean.
Also you must check the latest patches available for this system architecture.

Similar Messages

Last Trap: Data Access Error

Hello,
I don't know what the appropropriate forum to ask this would be; please
suggest another one if this is not the best one.
We have a PCI-Express board (that we developed) that we're attempting to
use in a Sparc system. It is an Ultra 25 (also says Ultra SPARC IIIi).
We've attempted to use both Solaris 9 and 10.
With our board in an x8 slot, the system will not boot. If our board
is in an x16 slot, the system boots okay and the system can access
the board properly. Our board is an x1 board.
The following error message is seen during boot attempts:
"ERROR:/pci@e,600000/pci@1/pci@0/usb@1c,1: Last Trap: Data Access Error"
In addition, systems are able to boot and access our boards properly when the
boards are in x4, x8, and x16 slots of x86 systems running Windows and other
operating systems.
Could anyone suggest what might be wrong?
Thanks,
Nathan

Hello Sane,
I'm seeing a wierd problem on a new v890 server...
Record the current OBP settings, then issue set-defaults.
If the problem persists, open a service case.
Michael

Data access error while running the script in fdm workbench script editor

Hello Experts,
I have been getting the error when i run the script in script editor of fdqm workbench client.this is the error
                          -2147467259 Data access error and it is navigating the error at line 30 about this script "Set rsAppend = DW.DataAccess.farsTable(strWorkTableName)"
Please revert me asap where i should load the data from peoplesoft to one of my planning database through fdm.
Thanks in advance...

Hi,
Thanks for your suggestion's here i am going to run the datapump script so while i am running in workbench it is throwing data access error.So as you guy's suggested i created one import format and added this script to that import format which is added to one of my location even it is throwing the same error.I am getting the error at this sentence   "strWorkTableName" I want to know what is this where it reflect's?So my question is Is there any difference while running data pump or integration script.Please let me know a detailed navigation steps to run this script's with out data access error to run these kind of scripts.
Note:Again my target is to load the data to planning database through fdqm which i am doing through sql statement's.
Suggest your valuable suggestion's
Thanks in advance...
I am getting the error at this sentence   "strWorkTableName" I want to know what is this where it reflect's?

0187 EAIA Data access error Lenovo Twist

When the error happend the systemboard was replaced (0187 EAIA Data access error on startup), and the error came back up again. Replaced the systemboard again and the error persists. Can't update eprom serial information because of this error. I currently have about 6 machines doing the same thing, and was wondering if anyone else had experianced this issue?

I get the same error on a brand new Lenovo Thinkpad S540 (+-1 month old). Besides that first issue I'm also getting these errors:
2200: Machine Type and Serial Number are invalid
2201: Machine UUID is invalid
These occur together and only in about one out of every ten boots.
Curious what's wrong here.

Data Access Error in OIM Scheduler

I have a scheduler task in OIM,which fetches the "*Manager Employee ID*" custom field from OIM and if that is not empty then updates the Manager ID for that user.
The scheduler task when run throws an Data Access error, every time it starts and closes.
The same Scheduler code is working fine in the UAT environment successfully, but throws the error "Data Access Error" in the Prod environment.
In the code there is a catch block for catching the "*tcDataSetException*" and this is where the error is thrown from.
When i looked in to the code i found that the "*tcUserOperationsIntf*" was initialized but not closed in the finally block. Will closing the "tcUserOperationsIntf" slove this problem or am i missing something ?
When is the Data Access Error occur??? There are other schedulers that are running fine in the prod environment.
Any help in this regard would be really helpful to me.
Thanks

I am getting the UDF using the Query.
I am placing the piece of code that i am using for your reference
try {
     //Get Users for who have got there manager empid and manager empid not set to null
     String msQuery1 = "select usr_key,usr_login, "+udf_Manager_EMPID+" from usr where "+udf_Manager_EMPID+" is not null " ;
          tcDataSet getMemberUsers = new tcDataSet();
          getMemberUsers.setQuery(getDataBase(), msQuery1);
          getMemberUsers.executeQuery();
          for (int i=0;i<getMemberUsers.getTotalRowCount();i++)
               getMemberUsers.goToRow(i);
               String managerEmpId = getMemberUsers.getString(udf_Manager_EMPID);
               logger.debug("the manager emp id that we get for the user is "+managerEmpId );
               long userKey = getMemberUsers.getLong("usr_key");
               String userid = getMemberUsers.getString("usr_login");//Users.User ID
               logger.debug("the userkey that we get for the user is "+userKey );
               String msQuery2 = "select usr_key from usr where "+udf_EmployeeID+"="+ managerEmpId ;
               tcDataSet getMemberUser = new tcDataSet();
                    getMemberUser.setQuery(getDataBase(), msQuery2);
                    getMemberUser.executeQuery();
                    long userassociatedwithmgrid=0;
                    for(int j=0;j<getMemberUser.getTotalRowCount();j++){
                    getMemberUser.goToRow(j);
                         userassociatedwithmgrid = getMemberUser.getLong("usr_key");
                         logger.debug("the user id that we get for the user's manager is "+userassociatedwithmgrid );
                         updateusermanager(userid,userassociatedwithmgrid);
} catch (tcDataSetException e)
          logger.error(e.getMessage() + " DataSetException");
In the above code the error is being thrown from the catch block as Data Access Error
As i told earlier this piece of code works fine in UAT but does not work in prod and throw the above error. The error is thrown from the line msQuery2
Thanks

Data Access Error

I am trying to load data into FDM and has "Data Access Error". The error log is following:
** Begin FDM Runtime Error Log Entry [2013-05-09 08:57:13] **
ERROR:
Code............................................. -2147217900
Description...................................... Incorrect syntax near the keyword 'Right'.
BULK INSERT Right..tWswang35856364529183 FROM N'\\usd1w436c\fdmdata\Right\Inbox\tWswang35856364529183.tmp' WITH (FORMATFILE = N'\\usd1w436c\fdmdata\Right\Inbox\tWswang35856364529183.fmt',DATAFILETYPE = N'widechar',ROWS_PER_BATCH=6185,TABLOCK)
Procedure........................................ clsDataManipulation.fExecuteDML
Component........................................ upsWDataWindowDM
Version.......................................... 1112
Thread........................................... 36452
IDENTIFICATION:
User............................................. swang
Computer Name.................................... USD1W436C
App Name......................................... Right
Client App....................................... WebClient
CONNECTION:
Provider......................................... SQLOLEDB
Data Server...................................... gsd1w027t,1404
Database Name.................................... Right
Trusted Connect.................................. False
Connect Status.. Connection Open
GLOBALS:
Location......................................... PSLoad
Location ID...................................... 749
Location Seg..................................... 3
Category......................................... FDMActual
Category ID...................................... 12
Period........................................... Jan - 2013
Period ID........................................ 1/31/2013
POV Local........................................ False
Language......................................... 1033
User Level....................................... 1
All Partitions................................... True
Is Auditor....................................... False
** Begin FDM Runtime Error Log Entry [2013-05-09 08:57:14] **
ERROR:
Code............................................. -2147217900
Description...................................... Data access error.
Procedure........................................ clsImpDataPump.fImportTextFile
Component........................................ upsWObjectsDM
Version.......................................... 1112
Thread........................................... 36452
IDENTIFICATION:
User............................................. swang
Computer Name.................................... USD1W436C
App Name......................................... Right
Client App....................................... WebClient
CONNECTION:
Provider......................................... SQLOLEDB
Data Server...................................... gsd1w027t,1404
Database Name.................................... Right
Trusted Connect.................................. False
Connect Status.. Connection Open
GLOBALS:
Location......................................... PSLoad
Location ID...................................... 749
Location Seg..................................... 3
Category......................................... FDMActual
Category ID...................................... 12
Period........................................... Jan - 2013
Period ID........................................ 1/31/2013
POV Local........................................ False
Language......................................... 1033
User Level....................................... 1
All Partitions................................... True
Is Auditor....................................... False
** Begin FDM Runtime Error Log Entry [2013-05-09 08:57:14] **
ERROR:
Code............................................. -2147217900
Description...................................... Data access error.
Procedure........................................ clsImpProcessMgr.fLoadAndProcessFile
Component........................................ upsWObjectsDM
Version.......................................... 1112
Thread........................................... 36452
IDENTIFICATION:
User............................................. swang
Computer Name.................................... USD1W436C
App Name......................................... Right
Client App....................................... WebClient
CONNECTION:
Provider......................................... SQLOLEDB
Data Server...................................... gsd1w027t,1404
Database Name.................................... Right
Trusted Connect.................................. False
Connect Status.. Connection Open
GLOBALS:
Location......................................... PSLoad
Location ID...................................... 749
Location Seg..................................... 3
Category......................................... FDMActual
Category ID...................................... 12
Period........................................... Jan - 2013
Period ID........................................ 1/31/2013
POV Local........................................ False
Language......................................... 1033
User Level....................................... 1
All Partitions................................... True
Is Auditor....................................... False
Your input is appreciated!

OK, so this is definitely bulk copy related and most likely file/path access as that is the case 9/10 times.
Off the top of my head, you could check security one of two ways:
From SQL Box
- RDP (Remote Desktop) or physically log onto the SQL box using the credentials of the account specified when you setup the app
- Attempt to open the folder specified in the error log
- ** If you get an error it should give you an idea as to why it is failing**
From Machine that is sharing the folder
- Open Windows Explorer and locate the folder
- Right click, select properties, then security
- Confirm that the user specified in the FDM config has directory access
Other suggestions
- Put Filemon / procmon on the SQL Box and monitor while you push the file through FDM. At some point filemon/procmon will show an attempt ot access the files specified in the bulk insert. This will give you a very good idea as to what is happening.
- Check the Eventlog on the box with the file share. Go to the Security section of logs. You should see a failed security attempt from the SQL box / username.

Data Access Error HFM to FDM

Hi
When I attempt to drill back from HFM to FDM the following error is generated. "Data Access Error"
An extract of the error log is below:
ERROR:
Code......................................... -2147217900
Description.................................. Data access error.
Procedure.................................... clsSQLMgr.fLocationsByIntersection
Component.................................... upsWObjectsDM
Version...................................... 931
Thread....................................... 7484
Can anyone help me to resolve this?
SSO is turned on and I have entered the required settings into the FDM Load Balance Server Config and the HFM Web Server Config. A link to FDM has been set up from my HFM application and FDM launches with SSO working correctly.
Any advice would be greatly appreciated.
Kind Regards
DeeDee

Hi DeeDee
Didya find solution to this as am facing a similar problem .

Reboot hangs and takes several minutes to reboot

Hello fellow archers I have a Vaio laptop and my system started to hang and takes several minutes to reboot.
I have no real clue as to why since poweroff works fine and reboot used to work fine.
I did a system update. And more recently migrated to systemd, may not be related
edit: I found a workaround. Adding the following to my grub kernel line
reboot=pci
But it does not reboot quite the same way, meaning the power led no longer goes off and back on.
Still haven't quite figured out why I can no longer reboot normally without this workaround.
Last edited by snoxu (2012-10-18 18:16:18)

I am also having this problem. When trying to reboot, I get an endless cycle of the BIOS screen, then "MACHINE ERROR", then back. Running the same dmesg command as snoxu results in a similar error message. I am forced to shutdown by holding the power button. Upon rebooting, I get an error message that all extensions have been turned off (using Gnome Shell). Then I have to logout and login.
Shutting down and then restarting works fine.
Additional info:
System76 Gazelle Professional laptop
syslinux, systemd, GDM, Gnome Shell

Data Access Error importing Large Files, which previously worked

Hi All,
I am trying to import files directly from the server (from inbox), these files worked earlier so I know there is nothing wrong with them. If I take 600 rows out of the file, and upload them, it imports fine, however if I attempt to import the entire file, which is 16 meg, I get the error "Data Access Error". Why could this be?
1. It had been working for days prior, but cant anymore.
2. A sample of the file works - pulling from the same file path.
3. I try other files (other months) that are comparable in size, 15 meg+, and none of them work. So it is indeed a file size issue.
what can I do to resolve it?
Thanks
ERROR:
Code............................................. -2147217900
Description...................................... Data access error.
Procedure........................................ clsImpProcessMgr.fLoadAndProcessFile
Component........................................ upsWObjectsDM
Version.......................................... 1111
Thread........................................... 4940
Edited by: tyson33 on Dec 29, 2009 9:22 AM

Hello,
A "Data Access Error" means that something happened at the database level; not at the FDM level. I would suggest you clear your error log, reproduce the error log and then look at the very first entry.
Also, I would suggest you possibly open an SR for further review.
Thank you,

Err.Description="Data access error."

This question pertains to FDM 9.3.1, ImportAction script, StartProcess event.
After successfully CREATEing a table and BULK INSERTING a file sans a few erroneous records using "DW.DataManipulation.fExecuteDML strSQL, True, True" or "DW.DataManipulation.fExecuteDML strSQL, False, True", I get
Err.Number=2147217900 and Err.Description="Data access error."
However, after explicitly defining a connection to the FDM database server and executing the same SQL against the same data, I get an error description that is much more useful for my users, Error.Number=-2147217900 and Err.Description="Bulk load data conversion error (truncation) for row x, column y (fieldname)."
I'd rather not establish a second connection to the FDM database server if I can avoid it. Any ideas as to why each method produces a different error message? How do I get fExecuteDML to return the useful description?
' Connect to the FDM database server
Set adoConn = CreateObject("ADODB.Connection")
adoConn.ConnectionString = API.DataWindow.Connection.PstrConnection
adoConn.CursorLocation = 3' adUseClient
adoConn.Open
' Create the ADODB Command object
Set adoComm = CreateObject("ADODB.Command")
adoComm.ActiveConnection = adoConn
adoComm.CommandType = 1' adCmdTable
On Error Resume Next
adoComm.CommandText = strSQL
adoComm.Execute

Larry - apologies for the incomplete response. I misunderstood your question to be "how do I change the error message that FDM displays" I assumed you were trying to modify the information bar display.
Glad you found something that helps you.

Managed Beans and Data Access Object

I have a question / need help understanding how to configure backing bean and model objects so that memory and object creation/deletion is done as efficiently as possible.
1. I have a .jsf page with a form and a commandbutton that submits the form inputs to a backing bean (enrollispbean is backing bean)
<h:commandButton value="Enter" action="#{enrollispbean.insert}"/>
2. The backing bean is used for form handling - the insert() method is used to read the data fields from the form and create a SQL string that will be submitted to a model object, DbInsert, that is used as a generic data access object that connects to the database and insert the SQL string:
public class EnrollIspBean {
private String beanvar1="";
private String beanvar2= "";
// DbInsert is data access object
private DbInsert dbinsert = new DbInsert();
public String insert (){
String sqlstmt;
sqlstmt = "INSERT INTO ispmain VALUES(beanvar1, beanvar2,..)"
dbinsert.insert(sqlstmt);
return "success"; }
3. DbInsert is the data access object that contains a method, insert(), that accepts a sql string to insert into the database. This method contains the code to obtain a connection from the database connection pool and then execute the sql statement (note: error checking code not shown):
public class DbInsert {
public void insert(String sqlstmt) throws SQLException {
Connection conn = null;
GetDBConnection getdbconnection = new GetDBConnection();
PreparedStatement stmt = null;
conn = getdbconnection.getdbconn();
stmt = conn.prepareStatement(sqlstmt);
stmt.executeUpdate();
stmt.close();
conn.close();
return;
Where I need help understanding is how to set up the scope for the managed beans and data access object. Currently, I have the backing bean within the session scope (using the facesconfig.xml file). My main question is how to set up the scope for the Data Access Object - currently I do not have it as a managed bean within facesconfig.xml. Instead I am creating a new instance within the backing bean:
private DbInsert dbinsert = new DbInsert();
Is this the best way to do this? Will the DBInsert object now be tied to the session scope of the backing bean (i.e., when backing bean is deleted, the DbInsert object will be deleted from session scope as well.)
Ideally I would like the data access object to be available as a shared object throughout the life of the application. When I was programming using a servlet approach, I would have created a servlet to load on startup. Now that I'm using java server faces, I'm confused about the scope / how to efficiently set up a data access object that I want to be available to all backing beans in the application.
tnanks for any help understanding this.
Tom

I was thinking about setting the data access object as application scope so that it can be used by an backing bean to execute sql statements.
If I do set it as application scope, however, if I do this, do I still need to declare a new instance of the object from within each bean that uses the object?
For example do I need to declare a new instance of the data access object from within the bean? or, should I assume that there is always an instance of the bean available in the application scope, and if so, how do I reference it from within the bean?
Bean Code:
public class EnrollIspBean {
// DbInsert is data access object
private DbInsert dbinsert = new DbInsert();
Finally, I understand performance may be an issue if I have one instance of the data access object available in the application scope - is there a way to make multiple instances available in the application scope?
thanks

Data Access Error when Importing a Multi-Load Text File

I am able to upload a file that contains 12 months of data with the following tags (and one line of data as example):
EnterpriseToHFM07-09
Actual
01/31/2007
12
R,N,P
C,A,V,V,V,V,V,V,V,V,V,V,V,V
FR.PADJ_LC,BRREV,372803807,355714043,405412167,414395204,453025792,449832777,524375729,419567061,411230079,469840787,432445947,384835661
After uploading, click on Import and receive a Data Access Error. Log is below. Any input is greatly appreciated.
** Begin FDM Runtime Error Log Entry [2010-12-02 10:13:02] **
ERROR:
Code............................................. -2147217900
Description...................................... Cannot bulk load because the file "\\gsd4w023c\FDMAPPS\FDMT\Inbox\tWmpus54349283242113.tmp" could not be opened. Operating system error code 5(Access is denied.).
BULK INSERT FDMDev1..tWmpus54349283242113 FROM N'\\gsd4w023c\FDMAPPS\FDMT\Inbox\tWmpus54349283242113.tmp' WITH (FORMATFILE = N'\\gsd4w023c\FDMAPPS\FDMT\Inbox\tWmpus54349283242113.fmt',DATAFILETYPE = N'widechar',ROWS_PER_BATCH=2221,TABLOCK)
Procedure........................................ clsDataManipulation.fExecuteDML
Component........................................ upsWDataWindowDM
Version.......................................... 1112
Thread........................................... 8324
IDENTIFICATION:
User............................................. 12345
Computer Name.................................... GSD980
App Name......................................... FDMT
Client App....................................... WebClient
CONNECTION:
Provider......................................... SQLNCLI10
Data Server...................................... FDMDS
Database Name.................................... FDMDev1
Trusted Connect.................................. False
Connect Status.. Connection Open
GLOBALS:
Location......................................... EnterpriseToHFM07-09
Location ID...................................... 749
Location Seg..................................... 3
Category......................................... Actual
Category ID...................................... 12
Period........................................... Jan - 2007
Period ID........................................ 1/31/2007
POV Local........................................ False
Language......................................... 1033
User Level....................................... 1
All Partitions................................... True
Is Auditor....................................... False
** Begin FDM Runtime Error Log Entry [2010-12-02 10:13:02] **
ERROR:
Code............................................. -2147217900
Description...................................... Data access error. File=fr_HypEnt_data_2007.DAT
Procedure........................................ clsMPLoader.fMultiImportText
Component........................................ upsWMPLoaderDM
Version.......................................... 1112
Thread........................................... 8324
IDENTIFICATION:
User............................................. mpus54964
Computer Name.................................... GSD400U
App Name......................................... FDMT
Client App....................................... WebClient
CONNECTION:
Provider......................................... SQLNCLI10
Data Server...................................... FDMDS
Database Name.................................... FDMDev1
Trusted Connect.................................. False
Connect Status.. Connection Open
GLOBALS:
Location......................................... EnterpriseToHFM07-09
Location ID...................................... 749
Location Seg..................................... 3
Category......................................... Actual
Category ID...................................... 12
Period........................................... Jan - 2007
Period ID........................................ 1/31/2007
POV Local........................................ False
Language......................................... 1033
User Level....................................... 1
All Partitions................................... True
Is Auditor....................................... False

Yes.
Please take the time to flag this response as helpful or correct if it helps you address the issue
http://forums.oracle.com/forums/ann.jspa?annID=1184
Edited by: TonyScalese on Dec 2, 2010 11:52 AM

'Data Access Error' while trying to delete period using Table Editor in FDM

Hi,
I'm trying to delete a period that has been entered wrongly using Tools->Table Editor option.
But when I try to 'Update Grid' after deleting the Period,I get 'Data Access Error'.
Could any one let me know how to solve the error.
Thanks in advance

Hi Kelly,
There is no data that is entered in that period.The data will be entered for that period next month.
POV is also not set to that period,but still the problem persists.
Thanks

Data access error during workflow- import in FDM

I am trying to perform import in FDM.But getting 'Data Access Error'.
Any suggestions on this......

Hello,
I have the same problem.
Can anyone help.
Here is the log error:
** Begin FDM Runtime Error Log Entry [2009-01-30-12:44:44] **
ERROR:
Code......................................... -2147217900
Description.................................. ORA-06550: line 2, column 13:
PL/SQL: ORA-00913: too many values
ORA-06550: line 2, column 1:
PL/SQL: SQL Statement ignored
ORA-06550: line 3, column 13:
PL/SQL: ORA-00913: too many values
ORA-06550: line 3, column 1:
PL/SQL: SQL Statement ignored
ORA-06550: line 4, column 13:
PL/SQL: ORA-00913: too many values
ORA-06550: line 4, column 1:
PL/SQL: SQL Statement ignored
ORA-06550: line 5, column 13:
PL/SQL: ORA-00913: too many values
ORA-06550: line 5, column 1:
PL/SQL: SQL Statement ignored
ORA-06550: line 6, column 13:
PL/SQL: ORA-00913: too many values
ORA-06550: line 6, column 1:
PL/SQL: SQL Statement ignored
ORA-06550: line 7, column 13:
PL/SQL: ORA-00913: too many values
ORA-06550: line 7, column 1:
PL/SQL: SQL Statement ignored
ORA-06550: line 8, column 13:
PL/SQL: ORA-00913: too many values
ORA-06550: line 8, column 1:
PL/SQL: SQL Statement ignored
ORA-06550: line 9, column 13:
PL/SQL: ORA-00913: too many values
ORA-06550: line 9, column 1:
PL/SQL: SQL Statement ignored
ORA-06550: line 10, column 13:
BEGIN
INSERT INTO tWselhou3242683022 (PartitionKey, CatKey, PeriodKey, DataView, Account, Entity, ICP, UD1, UD2, UD3, UD4, UD5, UD6, UD7, UD8, UD9, UD10, UD11, UD12, UD13, UD14, UD15, UD16, UD17, UD18, UD19, UD20, Desc1, Desc2, Attr1, Attr2, Attr3, Attr4, Attr5, Attr6, Attr7, Attr8, Attr9, Attr10, Attr11, Attr12, Attr13, Attr14, MemoKey, Amount ) VALUES (752, 12, '20090131', 'YTD', 'Required Field Missing.', 'Required Field Missing.', '', '', '', '', '', '', '', '', '', '', '', '', '', '', '', '', '', '', '', '', '', '', '', '', '', '', '', '', '', '', '', '', '', '', '', '', '', 0, 45645656,00);
INSERT INTO tWselhou3242683022 (PartitionKey, CatKey, PeriodKey, DataView, Account, Entity, ICP, UD1, UD2, UD3, UD4, UD5, UD6, UD7, UD8, UD9, UD10, UD11, UD12, UD13, UD14, UD15, UD16, UD17, UD18, UD19, UD20, Desc1, Desc2, Attr1, Attr2, Attr3, Attr4, Attr5, Attr6, Attr7, Attr8, Attr9, Attr10, Attr11, Attr12, Attr13, Attr14, MemoKey, Amount ) VALUES (752, 12, '20090131', 'YTD', 'Required Field Missing.', 'Required Field Missing.', '', '', '', '', '', '', '', '', '', '', '', '', '', '', '', '', '', '', '', '', '', '', '', '', '', '', '', '', '', '', '', '', '', '', '', '', '', 0, 456546564,00);
INSERT INTO tWselhou3242683022 (PartitionKey, CatKey, PeriodKey, DataView, Account, Entity, ICP, UD1, UD2, UD3, UD4, UD5, UD6, UD7, UD8, UD9, UD10, UD11, UD12, UD13, UD14, UD15, UD16, UD17, UD18, UD19, UD20, Desc1, Desc2, Attr1, Attr2, Attr3, Attr4, Attr5, Attr6, Attr7, Attr8, Attr9, Attr10, Attr11, Attr12, Attr13, Attr14, MemoKey, Amount ) VALUES (752, 12, '20090131', 'YTD', 'Required Field Missing.', 'Required Field Missing.', '', '', '', '', '', '', '', '', '', '', '', '', '', '', '', '', '', '', '', '', '', '', '', '', '', '', '', '', '', '', '', '', '', '', '', '', '', 0, 4556465454,00);
INSERT INTO tWselhou3242683022 (PartitionKey, CatKey, PeriodKey, DataView, Account, Entity, ICP, UD1, UD2, UD3, UD4, UD5, UD6, UD7, UD8, UD9, UD10, UD11, UD12, UD13, UD14, UD15, UD16, UD17, UD18, UD19, UD20, Desc1, Desc2, Attr1, Attr2, Attr3, Attr4, Attr5, Attr6, Attr7, Attr8, Attr9, Attr10, Attr11, Attr12, Attr13, Attr14, MemoKey, Amount ) VALUES (752, 12, '20090131', 'YTD', 'Required Field Missing.', 'Required Field Missing.', '', '', '', '', '', '', '', '', '', '', '', '', '', '', '', '', '', '', '', '', '', '', '', '', '', '', '', '', '', '', '', '', '', '', '', '', '', 0, 546,00);
INSERT INTO tWselhou3242683022 (PartitionKey, CatKey, PeriodKey, DataView, Account, Entity, ICP, UD1, UD2, UD3, UD4, UD5, UD6, UD7, UD8, UD9, UD10, UD11, UD12, UD13, UD14, UD15, UD16, UD17, UD18, UD19, UD20, Desc1, Desc2, Attr1, Attr2, Attr3, Attr4, Attr5, Attr6, Attr7, Attr8, Attr9, Attr10, Attr11, Attr12, Attr13, Attr14, MemoKey, Amount ) VALUES (752, 12, '20090131', 'YTD', 'Required Field Missing.', 'Required Field Missing.', '', '', '', '', '', '', '', '', '', '', '', '', '', '', '', '', '', '', '', '', '', '', '', '', '', '', '', '', '', '', '', '', '', '', '', '', '', 0, 654,00);
INSERT INTO tWselhou3242683022 (PartitionKey, CatKey, PeriodKey, DataView, Account, Entity, ICP, UD1, UD2, UD3, UD4, UD5, UD6, UD7, UD8, UD9, UD10, UD11, UD12, UD13, UD14, UD15, UD16, UD17, UD18, UD19, UD20, Desc1, Desc2, Attr1, Attr2, Attr3, Attr4, Attr5, Attr6, Attr7, Attr8, Attr9, Attr10, Attr11, Attr12, Attr13, Attr14, MemoKey, Amount ) VALUES (752, 12, '20090131', 'YTD', 'Required Field Missing.', 'Required Field Missing.', '', '', '', '', '', '', '', '', '', '', '', '', '', '', '', '', '', '', '', '', '', '', '', '', '', '', '', '', '', '', '', '', '', '', '', '', '', 0, 546,00);
INSERT INTO tWselhou3242683022 (PartitionKey, CatKey, PeriodKey, DataView, Account, Entity, ICP, UD1, UD2, UD3, UD4, UD5, UD6, UD7, UD8, UD9, UD10, UD11, UD12, UD13, UD14, UD15, UD16, UD17, UD18, UD19, UD20, Desc1, Desc2, Attr1, Attr2, Attr3, Attr4, Attr5, Attr6, Attr7, Attr8, Attr9, Attr10, Attr11, Attr12, Attr13, Attr14, MemoKey, Amount ) VALUES (752, 12, '20090131', 'YTD', 'Required Field Missing.', 'Required Field Missing.', '', '', '', '', '', '', '', '', '', '', '', '', '', '', '', '', '', '', '', '', '', '', '', '', '', '', '', '', '', '', '', '', '', '', '', '', '', 0, 654,00);
INSERT INTO tWselhou3242683022 (PartitionKey, CatKey, PeriodKey, DataView, Account, Entity, ICP, UD1, UD2, UD3, UD4, UD5, UD6, UD7, UD8, UD9, UD10, UD11, UD12, UD13, UD14, UD15, UD16, UD17, UD18, UD19, UD20, Desc1, Desc2, Attr1, Attr2, Attr3, Attr4, Attr5, Attr6, Attr7, Attr8, Attr9, Attr10, Attr11, Attr12, Attr13, Attr14, MemoKey, Amount ) VALUES (752, 12, '20090131', 'YTD', 'Required Field Missing.', 'Required Field Missing.', '', '', '', '', '', '', '', '', '', '', '', '', '', '', '', '', '', '', '', '', '', '', '', '', '', '', '', '', '', '', '', '', '', '', '', '', '', 0, 564,00);
INSERT INTO tWselhou3242683022 (PartitionKey, CatKey, PeriodKey, DataView, Account, Entity, ICP, UD1, UD2, UD3, UD4, UD5, UD6, UD7, UD8, UD9, UD10, UD11, UD12, UD13, UD14, UD15, UD16, UD17, UD18, UD19, UD20, Desc1, Desc2, Attr1, Attr2, Attr3, Attr4, Attr5, Attr6, Attr7, Attr8, Attr9, Attr10, Attr11, Attr12, Attr13, Attr14, MemoKey, Amount ) VALUES (752, 12, '20090131', 'YTD', 'Required Field Missing.', 'Required Field Missing.', '', '', '', '', '', '', '', '', '', '', '', '', '', '', '', '', '', '', '', '', '', '', '', '', '', '', '', '', '', '', '', '', '', '', '', '', '', 0, 564,00);
END;
Procedure.................................... clsDataManipulation.fExecuteDML
Component.................................... upsWDataWindowDM
Version...................................... 931
Thread....................................... 268
IDENTIFICATION:
User......................................... selhouda
Computer Name................................ FR900VM0044
App Name..................................... test
Client App................................... WebClient
CONNECTION:
Provider..................................... ORAOLEDB.ORACLE
Data Server..................................
Database Name................................ PARHYPT3.WORLD
Trusted Connect.............................. False
Connect Status.. Connection Open
GLOBALS:
Location..................................... LOCATION4
Location ID.................................. 752
Location Seg................................. 6
Category..................................... WLCAT
Category ID.................................. 12
Period....................................... janv - 2009
Period ID.................................... 31/01/2009
POV Local.................................... False
Language..................................... 1033
User Level................................... 1
All Partitions............................... True
Is Auditor................................... False
** Begin FDM Runtime Error Log Entry [2009-01-30-12:44:44] **
ERROR:
Code......................................... -2147217900
Description.................................. Data access error.
Procedure.................................... clsImpDataPump.fProcessSQLInsertValues
Component.................................... upsWObjectsDM
Version...................................... 931
Thread....................................... 268
IDENTIFICATION:
User......................................... selhouda
Computer Name................................ FR900VM0044
App Name..................................... test
Client App................................... WebClient
CONNECTION:
Provider..................................... ORAOLEDB.ORACLE
Data Server..................................
Database Name................................ PARHYPT3.WORLD
Trusted Connect.............................. False
Connect Status.. Connection Open
GLOBALS:
Location..................................... LOCATION4
Location ID.................................. 752
Location Seg................................. 6
Category..................................... WLCAT
Category ID.................................. 12
Period....................................... janv - 2009
Period ID.................................... 31/01/2009
POV Local.................................... False
Language..................................... 1033
User Level................................... 1
All Partitions............................... True
Is Auditor................................... False
** Begin FDM Runtime Error Log Entry [2009-01-30-12:44:44] **
ERROR:
Code......................................... -2147217900
Description.................................. Data access error.
Procedure.................................... clsImpDataPump.fImportTextFile
Component.................................... upsWObjectsDM
Version...................................... 931
Thread....................................... 268
IDENTIFICATION:
User......................................... selhouda
Computer Name................................ FR900VM0044
App Name..................................... test
Client App................................... WebClient
CONNECTION:
Provider..................................... ORAOLEDB.ORACLE
Data Server..................................
Database Name................................ PARHYPT3.WORLD
Trusted Connect.............................. False
Connect Status.. Connection Open
GLOBALS:
Location..................................... LOCATION4
Location ID.................................. 752
Location Seg................................. 6
Category..................................... WLCAT
Category ID.................................. 12
Period....................................... janv - 2009
Period ID.................................... 31/01/2009
POV Local.................................... False
Language..................................... 1033
User Level................................... 1
All Partitions............................... True
Is Auditor................................... False
** Begin FDM Runtime Error Log Entry [2009-01-30-12:44:44] **
ERROR:
Code......................................... -2147217900
Description.................................. Data access error.
Procedure.................................... clsImpProcessMgr.fLoadAndProcessFile
Component.................................... upsWObjectsDM
Version...................................... 931
Thread....................................... 268
IDENTIFICATION:
User......................................... selhouda
Computer Name................................ FR900VM0044
App Name..................................... test
Client App................................... WebClient
CONNECTION:
Provider..................................... ORAOLEDB.ORACLE
Data Server..................................
Database Name................................ PARHYPT3.WORLD
Trusted Connect.............................. False
Connect Status.. Connection Open
GLOBALS:
Location..................................... LOCATION4
Location ID.................................. 752
Location Seg................................. 6
Category..................................... WLCAT
Category ID.................................. 12
Period....................................... janv - 2009
Period ID.................................... 31/01/2009
POV Local.................................... False
Language..................................... 1033
User Level................................... 1
All Partitions............................... True
Is Auditor................................... False

Data Access Error when importing Standard Reports

After installation, when I try to import standard reports, I got a "Data Access Error".
FDM 9.3.1
Oracle 10g
In the fdm.err, I find the following description:
ORA-12899 : too long value for "MYFDMSCHEMA"."TREPORT"."REPORTDESC" (real 152, max 75).
It seems that reports descriptions are too long for my Oracle repository...
Any idea ?
Regards

Yes.
Please take the time to flag this response as helpful or correct if it helps you address the issue
http://forums.oracle.com/forums/ann.jspa?annID=1184
Edited by: TonyScalese on Dec 2, 2010 11:52 AM

Solaris 8 hangs and data access error on reboot

Similar Messages

Maybe you are looking for