Error querying dba_data_files

Hi all,
when i give the below mentioned query i got the following error...
select FILE_NAME from dba_data_files where TABLESPACE_NAME='TS_IIMS_REP_DAT_01';
Error
select FILE_NAME from dba_data_files where TABLESPACE_NAME='TS_IIMS_REP_DAT_01'
ERROR at line 1:
ORA-01157: cannot identify/lock data file 27 - see DBWR trace file
ORA-01110: data file 27: '+DATAREP/gicprod/datafile/ts_iims_rep_dat_01.256.632950853
than i checked diskgroup status for DATAREP
it was in dismount state and then i gave the command
alter diskgroup dsik mount;
dsikgrooup altered.
than again i gave the above query still i`m receiving same error...
in that diskgoup only we are having that datafile i need.
some one please tell me why
i cant find anythin in trace file..

Since you are saying the disk group in dismount stage and unable to mount, check the raw disk availability to the server? Is there any change?
You may shutdown the database and ASM. Start the ASM and check disk group status. Bring them to mount status and bring up the database.
Ashok

Similar Messages

Powerpivot Report 2010 - OLE DB or ODBC error: Query timeout expired; HYT00

0
I have report already developed by someone in powerpivot 2010 and deployed to sharepoint in powerpivot gallery library. The data source for this report is SQL Server 2008 r2. I have set the refresh options in sharepoint to run after business hours during
week end. When I check the refresh history it shows this error message "OLE DB or ODBC error: Query timeout expired; HYT00. An error occurred while processing the 'xxx' table. The current operation was cancelled because another operation in the
transaction failed..
I have tried to run the "Also refresh as soon as possible " just to check but same error message is shown.
This is the detailed error message details:
03/02/2014 21:06:55 03/02/2014 22:08:15 01:01:20 Failed
OLE DB or ODBC error: Query timeout expired; HYT00. An error occurred while processing the 'xxx' table. The current operation was cancelled because another operation in the transaction failed
Could anyone guide me on this issue? Truly appreciate your help in advance.

Hi asritha,
I would suggest you take a look at the following articles regarding how to configure PowerPivot data refresh in SharePoint Server:
Configure and Use Stored Credentials for PowerPivot Data Refresh:
http://technet.microsoft.com/en-us/library/ee210671(v=sql.105).aspx
Configure and Use the PowerPivot Unattended Data Refresh Account:
http://technet.microsoft.com/en-us/library/ff773327(v=sql.105).aspx
Note: Please ensure that the account have sufficient permission access to your data source.
In addition, please elaborate your PowerPivot data soure with more detail. If you are using SSAS cube, please try to increase "ExternalConnectionTimeout" property default value to see if this helps. Here is the similar thread for your reference,
please see:
http://social.technet.microsoft.com/Forums/en-US/35b26c06-9e6d-41e5-ae44-bfb1233510ac/ssas2008-ole-db-error-ole-db-or-odbc-error-query-timeout-expired-hyt00?forum=sqldatamining
Regards,
Elvis Long
TechNet Community Support

Can't get IVI Power Meter error query to work properly.

I have been trying to use the IviPwrMeter Error-Query.vi to read possible errors coming from the Power Meter. However, I have found that no errors can be detected using this vi. This is because the returned value 'status' is wired over to the 'error code' input of 'IviPwrMeter Error Converter.vi' and the status value will always be equal to VI_SUCCESS as the attached code signifies.
All of this code was generated by either LabWindows/CVI and/or LabView.
If I wire the error code output of 'IviPwrMeter_error_query' function to the error code input of 'IviPwrMeter IVI error converter.vi', the errors on the Power Meter is at least detected.
Am I doing something wrong here or are there other work arounds?
Source listing of driver call:
ViStatus _VI_FUNC age4418b_error_query (ViSession vi, ViInt32 *errCode,
                                        ViChar errMessage[])
    ViStatus    error = VI_SUCCESS;
    checkErr( Ivi_LockSession (vi, VI_NULL));
    if (errCode == VI_NULL)
        viCheckParm( IVI_ERROR_INVALID_PARAMETER, 2, "Null address for Error Code");
    if (errMessage == VI_NULL)
        viCheckParm( IVI_ERROR_INVALID_PARAMETER, 3, "Null address for Error Message");
if (!Ivi_Simulating(vi))                /* call only when locked */
     ViSession   io = Ivi_IOSession(vi); /* call only when locked */
     checkErr( Ivi_SetNeedToCheckStatus (vi, VI_TRUE));
     viCheckErr( viPrintf(io, "YST:ERR?"));
  viCheckErr( viScanf (io, "%ld,\"%256[^\"]", errCode, errMessage));
else
         /* Simulate Error Query */
     *errCode = 0;
     strcpy (errMessage, "No error.");
Error:
    Ivi_UnlockSession(vi, VI_NULL);
    return error;

Dennis,
I get the same results as you if I don't have a power meter connected. However, this doesn't supprise me because the session handle is probably checked at a higher level.
The calling hiearchy is as follows (I think, because I don't have all of the code) IviPwrMeter Error Query.vi -> IviPwrMeter_error_query (IviPwrMeter.dll) ->age4418b_error_query (age4418b.dll). I would guess that the session is validated in the second layer and not the bottom layer where the actual instrument error query is happening.
Something you may try. If you have any instrument, write a simple program to get a valid handle then call the error query using the error cluster to link them together. Set a breakpoint before the error query, run the program, use MAX to send an invalid command and create an error. Then resume your original program and see if an error is reported in the error cluster after executing the IVI error query.
Bob

Error query.vi in my D6000 single phase

hello everyone , recently I am using the Labview 2009
I am running the program LEM D6000 single phase.vi
but in the Error Query.vi(inside D6000 Config Measurement block) there is always a mistake, Error 1300,, because after the VISA read , there comes in a number and compared to those constant number, first row and first column is 16, which somtimes is smaller than the number comes in , so it gives the comparison result as T, Error happens
so I changed 16 to 64, no more errors comes up
So I wonder what is the real function of Error Query is , and why shall I change the constant number to avoid the errors, although I make it work, but I want to know why.
Thank you very much
Attachments:
lem_instruments_d6000.zip ‏781 KB

The error conditions and the Event Status Register should be documented in the instrument manual. Not sure where to start with the basics. There are individual bits in the ESR and the instrument will set specific ones depending on the actual error that the instrument detects. Are you familiar with Boolean math? Bit number 4 reflects a specific error. If you want to check to see if the bit is set, you would AND it with decimal 16 or binary 10000. If bit 1 is set, the result of the AND is 1. You decided to AND it with 64 (a check of bit 5) and by doing that, you are no longer checking to see if bit 4 is set. That is ignoring the error. If you want to ignore any errors, don't run the error query program. Changing the code is just plain wrong.

Performance Dialogue error - Query "Status Overview is already open in ano

Hi All,
We implemented ESS MSS on Portal 7.01 SP8. With With SAP_ESS 603 SP7 and BP_ERP5ESS 1.41 SP9
This is for country Qatar and it has made as a copy of GB as SAP doesnt provide any country structure for Qatar.
We are facing error in Performance Dialog saying "Query "Status Overview is already open in another session" when click / display button is clicked after selecting the Appriasal document in ESS.
This is working fine for all other countries and also this works fine if another country's portal role is assigned to same PRNR or test user.
We cant see any locks in backend / portal.
Please can someone help.

Hi Siddharth,
We have already checked and there were/are no locks in Sm12.
I tried deleting the locks using the mentioned program, in result is does say that ! query found but when I go to Portal and open the Performance Dialogue document , I still get the error Query " " is already open in another session
Note 1432358 is for SAP_BASIS >= 701 which is suitable for our case but, just wanted to check, Performance dialogue works fine for all other countries and only for this particular country it's not working.
We are able to replicate this in Development and Test, both the environments.
Also, when this particular user is assigned, another country's portal roles the problem doesnt occur.
Any clues?

Error querying fact: -2417217900 invalid column name

Dear Xperts
while validating script logic it gives error"error querying fact: -2417217900 invalid column name P_ACCT"
P_ACCT dimension created by me.
problem has started today while creating new script logic.
as old logic created earlier was sucessfully validated
new logic was created refering document 330 for bpc,so there is no scripting error
pls guide me through this.
thanks
kashyap

thanks for ur advice
i was able to validate logics previously.
i tried way you sugested but was unable to validate.
i also tried updating that dimension members but it was giving me some olap querry error while processing dimension after changing dimension members.
so finally i deleted that dimension created new one did whole process again
& was successfull
but i wanted to know why this error could have occured
thanks
kashyap

Executing Package -- Error querying fact: 7 - Out of memory

Hello,
I have a problem.
I am executing a package call Period Initialization.
It gives me an error.
End time --->1:33:08 PM - Date:12/22/2008
Error querying fact: 7 - Out of memory
I don't know why it gives me this error.
Can Someone help me????
I have to change a parameter in the Appset administration to take this out of memory
Thank you in advance
Pablo Mortera

Hi Pablo Mortera,
Data manager package tries to run the logic on all the members in data region at a time, loading all the fact values to temp tables. If the number of records to be processed are more that the memory allocated for the temp tables, you may get this error. One way to handle this is to restrict on the number of dimension members executed in a single go. YOu can do this by using
> *XDIM_MAXMEMBERSET DIMNAME=
for example try this,
> *XDIM_MAXMEMBERSET TIME=12
Kranthi

Change Own Data - System error: query could not be found

Hi Experts,
Please help me on the above issue.
Change Own data is not working in QA environment. Configuration changes related to Change own data does not prompt for a transport request. I have trasnsported T77WWW_WHO entries to QA.
Here is the table entry.
08     /SAPQUERY/HR_XX_PA_ESS     Y ESS_WHOS_WHO GB     SY000000000142     SY000000000143
I dont have any clue about this issue. No ST22 dump is also generated.
Thanks in advance.
Cheers
Jay

Critical Error
A critical error has occured. Processing of the service had to be terminated. Unsaved data has been lost.
Please contact your system administrator.
System error: query could not be found
System error: query could not be found:com.sap.pcuigp.xssfpm.java.FPMRuntimeException: System error: query could not be found
     at com.sap.pcuigp.xssfpm.java.MessageManager.raiseException(MessageManager.java:112)
     at com.sap.pcuigp.xssfpm.java.MessageManager.raiseException(MessageManager.java:122)
     at com.sap.xss.hr.cod.FcCodBusinessLogicComp.callRFCGetDetails(FcCodBusinessLogicComp.java:480)
     at com.sap.xss.hr.cod.FcCodBusinessLogicComp.onInit(FcCodBusinessLogicComp.java:228)
     at com.sap.xss.hr.cod.wdp.InternalFcCodBusinessLogicComp.onInit(InternalFcCodBusinessLogicComp.java:512)
     at com.sap.xss.hr.cod.FcCodBusinessLogicCompInterface.onInit(FcCodBusinessLogicCompInterface.java:115)
     at com.sap.xss.hr.cod.wdp.InternalFcCodBusinessLogicCompInterface.onInit(InternalFcCodBusinessLogicCompInterface.java:147)
     at com.sap.xss.hr.cod.wdp.InternalFcCodBusinessLogicCompInterface$External.onInit(InternalFcCodBusinessLogicCompInterface.java:227)
     at com.sap.pcuigp.xssfpm.wd.FPMComponent$FPM.attachComponentToUsage(FPMComponent.java:922)
     at com.sap.pcuigp.xssfpm.wd.FPMComponent$FPM.attachComponentToUsage(FPMComponent.java:891)
     at com.sap.pcuigp.xssfpm.wd.FPMComponent$FPMProxy.attachComponentToUsage(FPMComponent.java:1084)
     at com.sap.xss.hr.cod.start.VcCodStartComp.onInit(VcCodStartComp.java:196)
     at com.sap.xss.hr.cod.start.wdp.InternalVcCodStartComp.onInit(InternalVcCodStartComp.java:156)
     at com.sap.xss.hr.cod.start.VcCodStartCompInterface.onInit(VcCodStartCompInterface.java:161)
     at com.sap.xss.hr.cod.start.wdp.InternalVcCodStartCompInterface.onInit(InternalVcCodStartCompInterface.java:144)
     at com.sap.xss.hr.cod.start.wdp.InternalVcCodStartCompInterface$External.onInit(InternalVcCodStartCompInterface.java:220)
     at com.sap.pcuigp.xssfpm.wd.FPMComponent.doProcessEvent(FPMComponent.java:564)
     at com.sap.pcuigp.xssfpm.wd.FPMComponent.doEventLoop(FPMComponent.java:438)
     at com.sap.pcuigp.xssfpm.wd.FPMComponent.wdDoInit(FPMComponent.java:196)
     at com.sap.pcuigp.xssfpm.wd.wdp.InternalFPMComponent.wdDoInit(InternalFPMComponent.java:110)
     at com.sap.tc.webdynpro.progmodel.generation.DelegatingComponent.doInit(DelegatingComponent.java:108)
     at com.sap.tc.webdynpro.progmodel.controller.Controller.initController(Controller.java:215)
     at com.sap.tc.webdynpro.progmodel.controller.Controller.init(Controller.java:200)
     at com.sap.tc.webdynpro.clientserver.cal.ClientComponent.init(ClientComponent.java:430)
     at com.sap.tc.webdynpro.clientserver.cal.ClientApplication.init(ClientApplication.java:362)
     at com.sap.tc.webdynpro.clientserver.session.ApplicationSession.initApplication(ApplicationSession.java:756)
     at com.sap.tc.webdynpro.clientserver.session.ApplicationSession.doProcessing(ApplicationSession.java:291)
     at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessingPortal(ClientSession.java:733)
     at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessing(ClientSession.java:668)
     at com.sap.tc.webdynpro.clientserver.session.ClientSession.doProcessing(ClientSession.java:250)
     at com.sap.tc.webdynpro.clientserver.session.RequestManager.doProcessing(RequestManager.java:149)
     at com.sap.tc.webdynpro.clientserver.session.core.ApplicationHandle.doProcessing(ApplicationHandle.java:73)
     at com.sap.tc.webdynpro.portal.pb.impl.AbstractApplicationProxy.sendDataAndProcessActionInternal(AbstractApplicationProxy.java:869)
     at com.sap.tc.webdynpro.portal.pb.impl.AbstractApplicationProxy.create(AbstractApplicationProxy.java:229)
     at com.sap.portal.pb.PageBuilder.updateApplications(PageBuilder.java:1344)
     at com.sap.portal.pb.PageBuilder.createPage(PageBuilder.java:356)
     at com.sap.portal.pb.PageBuilder.init(PageBuilder.java:549)
     at com.sap.portal.pb.PageBuilder.wdDoRefresh(PageBuilder.java:593)
     at com.sap.portal.pb.PageBuilder$1.doPhase(PageBuilder.java:865)
     at com.sap.tc.webdynpro.clientserver.window.WindowPhaseModel.processPhaseListener(WindowPhaseModel.java:755)
     at com.sap.tc.webdynpro.clientserver.window.WindowPhaseModel.doPortalDispatch(WindowPhaseModel.java:717)
     at com.sap.tc.webdynpro.clientserver.window.WindowPhaseModel.processRequest(WindowPhaseModel.java:136)
     at com.sap.tc.webdynpro.clientserver.window.WebDynproWindow.processRequest(WebDynproWindow.java:335)
     at com.sap.tc.webdynpro.clientserver.cal.AbstractClient.executeTasks(AbstractClient.java:143)
     at com.sap.tc.webdynpro.clientserver.session.ApplicationSession.doProcessing(ApplicationSession.java:321)
     at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessing(ClientSession.java:684)
     at com.sap.tc.webdynpro.clientserver.session.ClientSession.doProcessing(ClientSession.java:250)
     at com.sap.tc.webdynpro.clientserver.session.RequestManager.doProcessing(RequestManager.java:149)
     at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doContent(DispatcherServlet.java:62)
     at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doPost(DispatcherServlet.java:53)
     at javax.servlet.http.HttpServlet.service(HttpServlet.java:760)
     at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
     at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:401)
     at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:266)
     at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:386)
     at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:364)
     at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:1039)
     at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:265)
     at com.sap.engine.services.httpserver.server.Client.handle(Client.java:95)
     at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:175)
     at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33)
     at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41)
     at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
     at java.security.AccessController.doPrivileged(AccessController.java:219)
     at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:104)
     at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:176)

Function of Error Query.vi?

Hello , I am confused of the function of Error Query, since I am really new in this field ,I hope I can learn sth here.
From the Fig111, I have some questions, VISA write in "*ESR?" and then VISA read 10 bytes, then the 999block get the decimal number from it , compare the number to 3 different constant number 16, 32 and 4, what we need is get a False from it ,otherwise error comes up
so can anyone explain the idea or principle behind it?
Attachments:
111.jpg ‏116 KB
lem_instruments_d6000.zip ‏781 KB

hi xyq102296,
I think those commands are queries to know about the status of hardware .
1)If *ESR?(some status register) is the query,then output will have the error put in the bit patterns,thats why they are checking if the 3,5 and 6th bit positions are 1's are not(and operation).if any bit position is 1,then corresponding error will be there.
2)Similarly STA HW?is the query to know the status of the hardware and the output of the visa read will give info about the error(checking the 2,4,and 6 th postions are 1's or not)
3)STA OP ?query to knwo the status of operation and output of the visa read will give info about the error...Now all the error are concatenated and the new string is compared with empty string..if empty string ,now error,if not error will be notfied as error cluster to the user.
Thanks and regards,
srikrishnaNF

Re:getting is error query desigher

Dear expert
i getting is error query desigher
Diagnosis
You have attempted to open query 0VENDOR from the Query Designer. However, this query does not exist in the database in the system to which you have made a connection.
System Response
Opening the query was terminated.
Procedure
Make sure that you have connected to the correct BW system. Note: The query may have been deleted by another user.
regards
pradeep

Hi Pradeep,
Look like some one deleted the Query, May be by mistake. Check the possiable ways..Insted of Executing it by technical name..Go to the data target and see if its still exists. Form there you wil be able to sort the issue ...
NB: Jai mam ...By the way BI content queries start with Zero ( Vendors: Overview : 0FIAP_C02_Q0001 ),
And would request you to be Polite to ppl on the form...because every one have there own way of expressing there question...Thanks for you'r support tho.

"GPIB error Query Interrupted" flashes on HP54542A

I've written a display and control program in Delphi 7 for the HP54542A. The program uses NI commands and the GPIB-32.dll library, per NI's recommendation. The program appears to work properly, but I frequently get the message "GPIB error-Query Interrupted" flashing on the scope screen. I've tried putting delays in the software after read and write commands, but that seems to have no effect. Any suggestions? The version of the GPIB-32.dll that I have is dated 1999. I'm using a fairly new NI PCMCIA card in a new Dell laptop.

tfowler,
Perhaps someone in the community has some experience with the HP54542A. We do have a newer GPIB driver which has a newer GPIB-32.dll that you could try:
NI-488.2 Download
We also have CVI and LabVIEW instrument drivers for this instrument that you could try out (since you are using Delphi you could at least check out what the drivers are doing and get some ideas):
54542A Driver Downloads
Craig H.

SSRS Error : Query execution failed for dataset 'dataSet'. (rsErrorExecutingCommand) Semantic query execution failed. Invalid object name 'RPT.*********'. (rsSemanticQueryEngineError)

I am new to SSRS and I am trying to migrate reports from 2008 to 2012. As I have so many reports to migrate, I simply got the back up of ReportServer,
ReportServerTempDB, and Encryption Key and restored them to test environment. I made necessary configuration from RS configuration tool. I am able to see the reports now when I browse //hostname/reports. But when I open any particular report I am getting some
error.
· An error has occurred during report processing.
(rsProcessingAborted)
Query execution       failed for dataset 'dataSet'.
      (rsErrorExecutingCommand
Semantic query        execution failed. Invalid object name
       'RPT. ******'. (rsSemanticQueryEngineError)
****** - I am assuming this is a custom data class.
Does anyone have insight on this? or any better way that I can migrate the reports to new server with less efforts.
I don’t have the reports solution file to deploy the reports, so I have followed backup and restore process.

Hi Kishore237,
According to your description, you migrated some reports from Reporting Services (SSRS) 2008 to 2012. Now you get error when accessing the reports on SSRS 2012. Right?
In this scenario, did you modify the report data source in database after migration? You can try to open the report in Report Builder or Report designer and check the report dataset. If you can preview the report in Report builder or Report designer,
please try to redeploy the report to Report Server. If it is still not working, please try to restore the database from backup. And for migrating reports, please follow the "Content-Only Migration" in the link below:
http://msdn.microsoft.com/en-us/library/ms143724(v=sql.110).aspx
If you have any question, please feel free to ask.
Best Regards,
Simon Hou

Error querying OLAP universe based on BEx query

Hi all,
I have a problem extracting larger (more than 80 000 rows) amounts of data through querying an OLAP universe with WebI.
The error is:
Query 1 - NAME_OF_THE_QUERY
A database error occurred. The database error text is: Error in MDDataSetBW.GetCellData. &INCLUDE INCL_INSTALLATION_ERROR. (WIS 10901)
The error occurs when I define larger scope of analysis in the query (four levels). With more modest scope (three levels or less) it's working OK. I need larger data set (more than 200 000 rows) to be populated at night through scheduling the report. We can't afford shrink the scope of analysis because it will hit the BW server during the day when it's needed by other users.
Besides this the speed of the report refresh is very slow - more than 3 minutes per just 400 rows of data. I'm still unable to identify the source of the problem with this slowdown. Executing the same query over the web through the SAP BW BEx Viewer is much much faster - just 3 seconds. Maybe the reason for this is that the BEx viewer aggregates data on the higher level of the hierarchy rather than down to transaction level (like we do by expanding the scope of analysis).
Anyway, if anyone have ideas about the error above I'll be very grateful if you share your thoughts. Thanks!
Our environment:
BO EDGE BI 3.1, standard
SAP BW 3.0
SAP Integration Kit (all transports installed)
BW user with full access

Ingo,
Could you point me to an official SAP document regarding the 1 million cells limitation, which describes the exact version and patch level for SAP BW which removes this limitation? It will be very helpful for me because I have to convince the client to migrate BW from 3.0 to 7.01 if it will solve this limitation.
Thank you in advance!
Ivan
BTW I have installed SP2 + FP2.1 and now the SAP integration is not functional, but I have opened another thread for this problem.

OBE-15065: Syntax error query builder

Hello
i am using the below sql query.
SELECT (
A.emp ||
'200' ||
LPAD((SELECT COUNT(*) FROM TRANSACTIONS WHERE TRANSACTIONS.PROCESSED ='N'),6,'0') ||
LPAD((SELECT SUM(AMOUNT) FROM TRANSACTIONS WHERE TRANSACTIONS.PROCESSED ='N'),10,'0') ||
'000000000000' ||
LPAD(A.ORIGIN,10,' ') ||
RPAD(NVL(A.MSGAUTHCODE,' '),19,' ') ||
RPAD(NVL(A.RESERVED,' '),6,' ') ||
RPAD(A.IMDDEST,8,' ') ||
LPAD(A.BTNUMBER,7,'0'))
FROM CONTROL_TABLE A
This query works fine in sql*plus.
i am placing this query in report data wizard and the query builder gives error "OBE-15065: Syntax error"
the report i am developing is to a delimited output as a fixed length falt file.
because of this query whenever i try to export using desformat=delimite and destype=file in system parameters. the report builder crashes.
have anyone faced this sort of problem.
is there something wrong with the query and iam doing it in wrong way in the reports.
please give your suggestions
thanks in advance
krishna

You haven't said what version of Oracle or what version of Query Builder you are using. There are things that work in SQL, but not in PL/SQL or various tools, especially in older versions. A select statement within a select clause is one of those things that gets rejected. Usually, the easiest way to fix it is to move the select statement from the select clause to the from clause. Please try the following and see if it solves your problem:
SELECT A.emp
|| '200'
|| LPAD (b.b_count, 6, '0')
|| LPAD (c.c_count, 10, '0')
|| '000000000000'
|| LPAD (A.ORIGIN, 10,' ')
|| RPAD (NVL (A.MSGAUTHCODE, ' '), 19, ' ')
|| RPAD (NVL (A.RESERVED, ' '), 6, ' ')
|| RPAD (A.IMDDEST, 8, ' ')
|| LPAD (A.BTNUMBER, 7, '0')
FROM CONTROL_TABLE A,
(SELECT COUNT (*) AS b_count
FROM TRANSACTIONS
WHERE TRANSACTIONS.PROCESSED ='N') b,
(SELECT SUM (AMOUNT) AS c_count
FROM TRANSACTIONS
WHERE TRANSACTIONS.PROCESSED ='N') c

Error: Query could not be saved due to problem in transport

Hi all,
This is the error msg i'm getting when i'm trying to save a new query. what could be the possible problem? And how should i go about solving it.
Thanks in Advance.
Mav.

Please check OSS Note 533413 and related notes 194051 and 337950.

Error querying dba_data_files

Similar Messages

Maybe you are looking for