Query transport error

Hi All,
While transporting query......i.e frm AWB.......transport connector........select objects and when i select required query and transferring i am getting following error
Object '0FIN_REP_SIMPL_1_EHP3' (AREA) of type 'InfoArea' is not available in version 'A'.
Please help me on this.
Regards

Hi,
I think u r collected query all objects( in collection mode u r used before after )so it is collectd the all objects on depending this query,
so at the time of collections u collect the Query elements alone not all objects
collect it freshly and do the once again transport.
Thanks & Regrdsa
sathish

Similar Messages

Query transport error message

Dear All,
Having trouble transporting a query. In the log, it has the following error message:-
"Start of the after-import method for object type R3TR ELEM (Activation Mode)
Message no. R7501 "
Not sure if this is the only problem, because there are several red error messages, but the above message is the first one in the list.
Regards, Frederick

Hi Frederick,
Do the error messages talk about particular elements being missing? Try to collect the query in RSA1 > Transport Connection and see if there are any elements that have $TMP data package...correct this and try to put into a fresh request and transport again.
Hope this helps...

SAP query transport error - need help

hello,
The system is throwing the following error when importing the query from development to QA client.
We already have the query imported the first time without errors. This is happening with subsequent transports if there is a change or any modification to the query.
Below is the error log from SAP regarding the failed transport :
R3TRAQQUFI was repaired in this system
Message no. TW104
Diagnosis
Object R3TRAQQUFI is in repair status. Therefore, it cannot be imported.
System Response
The object is not imported.
Procedure
If you still want to import the object, release the relevant repair and repeat the import.
Please help
Thanks in advance.

Hi
Here I am sending the step by step procedure for the SAP Query. Hope this helps you, if so please issue points.
1. Go to SQ02 .
Select Environment -> Query Areas
Select Standard Area (Client specific) as show below
2. Select Environment -> Transports
Select Import radio button
Check Overwriting allowed (only with import/upload/copy)
Remove Check for Test Run
Select Transport InfoSets and queries radio button
Fill Infoset and Query with corresponding names
Fill Import option with transport request number.
3. Click on Execute button
With this it will be done.
Thanks for your patience

Bex Query Transportation Error

Hi Guru's
While i try to access bex query for transportation using transport connection>queryElements>Query, sap throws Dump Error.
Is any body came across with this pls help me for solution.
Asap.

Hi,
This happens whenever there is not a sufficient memory available for processing. This can happen with any activity in the system like data loading, deletion, creation of objects etc.
Please ask your basis team to make sure that there is sufficient memory (tablespace) available in the system.
This will solve the issue.
Regards,
Yogesh

Transport Error from Dev to QA.

Hi All,
We r facing transport error while transporting req from Dev to QA,
Created queries in dev and try to trasport in QA.
Error:
Execution of programs after import (XPRA)
Transport request   : BD1K922532
System              : BQ1
tp path             : tp
Version and release: 372.04.29 700
Execution of programs after import (XPRA)
End date and time : 20091022031634
Ended with return code: ===> 8 <==
what could be the reason?
Regards,
SD

Hi.
I have collected all neccessary object which query contains, but after releasing the request it shows the message,
The request contains message that have already been edited & transported to other projects. To avoid overshooter problem when importing you need to create dependency information for the request with which object were last transported. The requiered information is listed here together with the existing information.
Should i go ahed with above message???? Is there any dependency?
Regards,
SD

Query running error

Hi, all.
In our PROD system we faced one problem. When we run query we get error
"Cannot create characteristic combination: type \BI0\0100000100" doesn't exit"
"Special situation CX_SY_CREATE_DATE_ERROR"
I think we have problem with temporary database objects what is described in SAP note 1139396. And we execute report "SAP_DROP_TMPTABLES", but it doesn't help.
Can anybody help us with this problem?
wbr, Fanil.

This probably won't solve your issue... but have you tried to regenerate your query using RSRT -> Generate button? I've found that this feature has helped resolved some query execution errors after transporting.
Can you give us any information about what dates are used in your query (standard or custom, any variables created on these date InfoObjects?). Thanks!

ABAP Query transports not handled by CHARM

Hi,
How should ABAP query transports be handled in CHARM??
The ABAP query transport tool doesn't allow picking a transport that is already created (Own transport), it creates a new transports which is outside of CHARM. I had to assign the objects in the transport manually to the appropriate CHARM transport.
Any ideas???
ABAP query don't seem to be using the standard transport tool.
Thanks
Stephane

Hi
Instead of assigning the objects you can directly assign the trasnports to the charm task list of the project
check q22 (registerting transport created outside of charm)
Change Request Management scenario: Usual questions and known errors
hope it clarifies
regards
prakhar

ABAP Query Transport request related

Hi,
I have created a Abap query,
1) User group
2)Infoset
3) Query
But when i transport the request in to Quality, I can see only Infoset, not able to see User group and query which i created in the
Development
Please suggest, is this std behaviour or is anything missed
Rgds,
Jai

Thanks to all,
I just created TR with new package for user group and included ifoset and query in the same TR
and imported, issue is resolved
But my question is,where we can utilize below help material, I have spent much time to understand below given explaination and finally left without any conclusion
Short text
SAP Query: Transport tool
Description
The report RSAQR3TR handles all tasks concerning the transport of queries, InfoSets and user groups.
General information
Queries, InfoSets and user groups are stored in the table AQDB. This table is client-specific. For the transport of queries, InfoSets and user groups, there is a special client-independent transport table called TAQTS. You can carry out transports either
·     from a client (source client) of an SAP system to another client (target client) in the same SAP system or
·     from a client (source client) of an SAP system (source system) to a client (target client) in another SAP system (target system).
In both cases, you have to perform similar actions.
The objects to be transported must first be copied from the source client using an export from the table AQDB into the transport table TAQTS. At the same time, a transport request is created for the transport system that includes all entries created by the export from table TATQS (transport dataset). The name of this transport request conforms to the transport system naming conventions (sysKnnnnnn) and is included in the export log. The transport dataset is stored in the table TAQTS under a key which matches the name of the transport request.
If you are transporting within one SAP system (from one client to another), you can import the transport dataset from the target client. The name of the transport request to use for this purpose is that specified during the export, since it should match the key of the transport dataset in the table TAQTS. With this import, the transport dataset is read from the transport table TAQTS and inserted into the table AQDB, where extensive checks ensure that there are no inconsistent statuses in the table AQDB.
If you are transporting from one SAP system to another, you must first use the transport system to release and export the transport request generated by the export. This transports the transport dataset from the transport table TAQTS into the target system. Then, you can import from the target client of the target system, as described above.
The transport datasets generated by exports in the transport table TAQTS are not deleted after successful import unless this is explicitly requested. Therefore, you can import a transport dataset several times (when copying a functional area to several different clients, for example).
This report handles exports (generation of transport datasets), imports (reading of transport datasets) as well as the management (display and deletion) of transport datasets.
As transport action, you must specify one of the values EXPO (export), IMPO (import), SHOW (display transport dataset) or DELE (delete transport dataset).
Transport action EXPO (exports)
If you select the 'Test only' parameter when exporting (no blank characters), the system determines only those queries, InfoSets and user groups that would be selected according to the selections for transport described below and generates an appropriate log. A transport dataset is not generated in the table TAQTS. This allows you to check whether a selection really includes the queries, InfoSets and user groups to be transported.
With exports, there are four different options for selecting objects (user groups, InfoSets, queries) to be transported. These are 'Transport of user groups', 'Transport of InfoSets', 'Transport of InfoSets and queries' and 'Transport of queries'. You must choose exactly one of these transport types.
In each case, you can also define an import option depending on the transport type. This allows you to determine how the transport dataset is inserted in the table AQDB of the target client during a later import.
The import options, each of which has an abbreviated syntax,
are as follows:
REPLACE or R
MERGE    or M
GROUP=ug or G=ug    (ug = name of a user group)
UNASSIGN or U
If you use the transport type 'Transport of user groups', all user groups are transported according to the select option 'user groups' and the selected import option. The import options REPLACE and MERGE are allowed.
If you use the transport type 'Transport of InfoSets', all InfoSets are transported according to the select option 'InfoSet' and the selected import option. The import options REPLACE, MERGE, GROUP=ug and UNASSIGN are allowed.
If you select the transport type 'Transport of InfoSets and queries', all InfoSets are transported according to the select option 'InfoSets' and the selected import option. The import options REPLACE and MERGE are allowed. Also, all queries are transported for each functional area selected, according to the select option 'queries'. In this case, the user groups of the queries are irrelevant and only the import option REPLACE is allowed.
This transport type allows you to transport a modified InfoSet and all the associated queries.
For the transport type 'Transport of queries', all queries are transported according to the select option 'User groups' and the select option 'Queries' as well as the selected import option. The import options REPLACE and GROUP=ug are allowed.
The export log displays which user groups, which InfoSets and which queries are transported, as well as the import options used.
Transporting a user group
Transporting a user group means transporting all members of the group from the source client. However, the InfoSet assignment to the user group in the source client is NOT transported.
The import option REPLACE first deletes all members of the group in the target client and then enters the members from the source client.
The import option MERGE leaves all members of the group assigned in the target client and adds the members of the group from the source client.
Entering a new member in a user group in the target client is possible only if a user master record exists.
In the target client, the assignment of InfoSets to this user group remains.
Transporting an InfoSet
Transporting an InfoSet means transporting the InfoSet and the InfoSet assignment to user groups in the source client.
Importing an InfoSet is possible only if the same logical database exists in the target client. Extensive checking is also performed to ensure that there are no inconsistencies between the InfoSet and the logical database.
The import option REPLACE first deletes the assignment of the InfoSet to user groups in the target client, provided there are no queries dependent on the InfoSet. The InfoSet is then transported to the target client and the assignment of the InfoSet to user groups is copied from the source client, if user groups also exist in the target client.
The import option GROUP=ug first deletes the assignment of the InfoSet to user groups in the target client, provided there are no queries referring to the InfoSet. The InfoSet is then transported to the target client and assigned to the user group ug of the target client, if such a user group exists.
The import option MERGE leaves the assignment of the InfoSet to user groups in the target client and transports it to the target client. It then copies the assignment of the InfoSet to user groups from the source client if user groups also exist in the target client.
The import option UNASSIGN first deletes the assignment of the InfoSet to user groups in the target client, provided there are no queries referring to the InfoSet. The InfoSet is then transported to the target client. No assignment of the InfoSet to user groups is performed.
Transporting a query
Transporting a query means only the query itself is transported.
Importing a query is possible only if a corresponding user group (see below) and a corresponding InfoSet exist in the target client and if the InfoSet is assigned to the user group. To demonstrate the effect of the import options, suppose that the query has the name QU and belongs to the user group BQ in the source client.
The import option REPLACE overwrites the query QU of the user group BQ in the target client if the user group exists.
The import option GROUP=ug overwrites the query QU of the user group UG in the target client if the user group exists. In this case, the query is explicitly assigned to a user group in the target client. This target user group may be differnet from the user group in the source client.
Transport action IMPO (imports)
If you choose the 'Test only' parameter with imports, only a test import is performed. This means that the system performs checks as for a real import and generates an import log. The import log contains information on the locks that have to be set. With a test import, you can check whether a transport dataset can be imported without any problem and which changes it would make in the table AQDB of the target client. A test import itself never makes changes in the table AQDB of the target client.
All transport datasets are imported according to the select option 'transport request'. In this case, the system outputs a detailed log of all checks carried out and all changes made in the table AQDB.
If you select the parameter 'Delete after successful import', the transport dataset in the table TAQTS is deleted after the import of each transport dataset if no errors occur during the import.
Transport action SHOW (display)
All transport datasets included in the transport table TAQTS are output with name (also the name of the transport request) and contents in the form of an overview.
Transport action DELE (delete)
All transport datasets are deleted according to the select option 'transport request'. To avoid unintentional deletion, the select option 'transport request' must contain values, meaning that the transport action DELE is not performed if this select option is empty.
Transport of ABAP Query
I am involved in this upgrade project to 4.7
The users are not able to find any reports (in QA System) which were there before the upgrade in SQ01. But they can see them in production which is not yet upgraded. They want me to copy all the reports to the QA system now....I dont have any idea how to do that.
I remember a similar problem upgrading to 4.6C from 4.5B ......
Take a look at OOS note 672784.
You can transport queries between systems in SQ02 (hit the lorry button) or run program RSAQR3TR.
You download the infosets, queries etc into a file and load them into whichever system you wish.
Just wanted to share my experience of transporting queries:
I needed to move a user group, 2 infosets and 3 queries from a 4.6 system to a 4.7 system.
When I tried doing this via the SQ* transactions I did not get the import/export option, so instead ran RSAQR3TR.
Step 1. Run RSAQR3TR in 'old' system. Select EXPORT and specify the objects to be transported.
(System includes these in an automatically created transport request)
Step 2. Release this transport and request it be transported to 'new' system.
(This results in the entries being populated in transport table AQTDB in 'new' system).
Step 3. Run RSAQR3TR in 'new' system. Select IMPORT and tick the Overwrite checkbox. Specify the transport number in the field labelled 'dataset with imports'.
(RSAQR3TR gives the message that stuff has been imported OK).
Step 4. In my example I still couldn't find the queries, so ran RSAQR3TR one more time, this time specifying 'Copy Standard Area -> Global Area'.
(Now my queries etc were available in new system).
Perhaps there are better ways, but after 1.5 days of struggling I was glad to get this far.
regards,
Jai

Transport Error When dev to Quality

Transport Error on Quality System
Hi Gurus,
I can face an error when moving query in dev to quality,
Error when activating element 497HY34X0YTB2D1KDTUFYWP4I
Element 497HY3CLJXF0KZL0JNWS8YNUA is missing in version M
Element 497HY59QAKUE8MG206HURGCAA is missing in version M
Please send me your valuable suggestion,
Its very urgent,
Thanks

Dear,
Transporting queries is little different than transporting other objects..
Did you follow the right way..
Kindly check against :
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/3010ba90-0201-0010-2896-e58547c6757e
Also see the discussion :
Query transport
Thanks

Query transport

HI SDN,
A query transport is failed due to missing of Query object(Query name) and a variable. I have collected those those two elements in differerent request and transported sucessfully. Now in which sequence these transports should be sent to PRD?
Thanks

hi,
i think this failure normally happened to the query that has been transported when we add a new variable to the query, since the transported query changes will be recorded in BEx request and the new variable won't be recorded anywhere.
we transport the BEx request before the new variable, then we find out error,
and send a new request to transport the new variable, and re-import again in PRD the BEx request (you can mark to let the request can be transported again)
so i think if you remember to transport the variable first then it's fine but if you forget, still you can re-import BEx again.
hope this helps.

Redo Transport Error

I am facing following errors , first error is on production database and second error is on physical standby database.
1. ORA-16778: redo transport error for one or more databases
2. ORA-01017: invalid username/password; logon denied
I study above messages but could not resolve. Now i shall be v v thankful if someone can help me in resolving errors, in simple step-by-step way.
Thank in advance

1. ORA-16778: redo transport error for one or more databases
16778, 00000, "redo transport error for one or more databases"
// *Cause: The redo transport service was unable to send redo data to one
//          or more standby databases.
// *Action: Check the Data Guard broker log and Oracle alert log for
//          more details. Query the LogXptStatus property to see the
//          errors.2. ORA-01017: invalid username/password; logon denied
Provide valid username/password
Post Operating System (OS) name & version for DB server system.
Post results of
SELECT * from v$version

Error: ORA-16778: redo transport error for one or more databases

Hi all
I have 2 database servers"Primary database and physical standby" in test environment( before going to Production)
Before Dataguard broker configuration , DG setup was running fine , redo was being applied and archived on phy standby.
but while enabling configuration i got "Warning: ORA-16607: one or more databases have failed" listener.ora & tnsnames.ora are updated with global_name_DGMGRL
Please help me how can i resolve this issue .Thanks in advance.
[oracle@PRIM ~]$ dgmgrl
DGMGRL for Linux: Version 10.2.0.1.0 - Production
Copyright (c) 2000, 2005, Oracle. All rights reserved.
Welcome to DGMGRL, type "help" for information.
DGMGRL> connect sys
Password:
Connected.
DGMGRL> show configuration
Configuration
Name: test
Enabled: YES
Protection Mode: MaxPerformance
Fast-Start Failover: DISABLED
Databases:
prim - Primary database
stan - Physical standby database
Current status for "test":
Warning: ORA-16607: one or more databases have failed
DGMGRL> show database
show database
^
Syntax error before or at "end-of-line"
DGMGRL> remove configuration
Warning: ORA-16620: one or more databases could not be contacted for a delete operation
Removed configuration
DGMGRL> exit
[oracle@PRIM ~]$ connect sys/sys@prim as sysdba
bash: connect: command not found
[oracle@PRIM ~]$ lsnrctl stop
LSNRCTL for Linux: Version 10.2.0.1.0 - Production on 08-OCT-2006 19:52:30
Copyright (c) 1991, 2005, Oracle. All rights reserved.
Connecting to (DESCRIPTION=(ADDRESS=(PROTOCOL=IPC)(KEY=EXTPROC1)))
The command completed successfully
[oracle@PRIM ~]$ lsnrctl start
LSNRCTL for Linux: Version 10.2.0.1.0 - Production on 08-OCT-2006 19:52:48
Copyright (c) 1991, 2005, Oracle. All rights reserved.
Starting /u01/app/oracle/product/10.2.0/db_1/bin/tnslsnr: please wait...
TNSLSNR for Linux: Version 10.2.0.1.0 - Production
System parameter file is /u01/app/oracle/product/10.2.0/db_1/network/admin/listener.ora
Log messages written to /u01/app/oracle/product/10.2.0/db_1/network/log/listener.log
Listening on: (DESCRIPTION=(ADDRESS=(PROTOCOL=ipc)(KEY=EXTPROC1)))
Listening on: (DESCRIPTION=(ADDRESS=(PROTOCOL=tcp)(HOST=PRIM)(PORT=1521)))
Connecting to (DESCRIPTION=(ADDRESS=(PROTOCOL=IPC)(KEY=EXTPROC1)))
STATUS of the LISTENER
Alias LISTENER
Version TNSLSNR for Linux: Version 10.2.0.1.0 - Production
Start Date 08-OCT-2006 19:52:48
Uptime 0 days 0 hr. 0 min. 0 sec
Trace Level off
Security ON: Local OS Authentication
SNMP OFF
Listener Parameter File /u01/app/oracle/product/10.2.0/db_1/network/admin/listener.ora
Listener Log File /u01/app/oracle/product/10.2.0/db_1/network/log/listener.log
Listening Endpoints Summary...
(DESCRIPTION=(ADDRESS=(PROTOCOL=ipc)(KEY=EXTPROC1)))
(DESCRIPTION=(ADDRESS=(PROTOCOL=tcp)(HOST=PRIM)(PORT=1521)))
Services Summary...
Service "PLSExtProc" has 1 instance(s).
Instance "PLSExtProc", status UNKNOWN, has 1 handler(s) for this service...
Service "PRIM_DGMGRLL" has 1 instance(s).
Instance "PRIM", status UNKNOWN, has 1 handler(s) for this service...
The command completed successfully
[oracle@PRIM ~]$ lsnrctl stop
LSNRCTL for Linux: Version 10.2.0.1.0 - Production on 08-OCT-2006 19:54:46
Copyright (c) 1991, 2005, Oracle. All rights reserved.
Connecting to (DESCRIPTION=(ADDRESS=(PROTOCOL=IPC)(KEY=EXTPROC1)))
The command completed successfully
[oracle@PRIM ~]$ lsnrctl start
LSNRCTL for Linux: Version 10.2.0.1.0 - Production on 08-OCT-2006 19:54:59
Copyright (c) 1991, 2005, Oracle. All rights reserved.
Starting /u01/app/oracle/product/10.2.0/db_1/bin/tnslsnr: please wait...
TNSLSNR for Linux: Version 10.2.0.1.0 - Production
System parameter file is /u01/app/oracle/product/10.2.0/db_1/network/admin/listener.ora
Log messages written to /u01/app/oracle/product/10.2.0/db_1/network/log/listener.log
Listening on: (DESCRIPTION=(ADDRESS=(PROTOCOL=ipc)(KEY=EXTPROC1)))
Listening on: (DESCRIPTION=(ADDRESS=(PROTOCOL=tcp)(HOST=PRIM)(PORT=1521)))
Connecting to (DESCRIPTION=(ADDRESS=(PROTOCOL=IPC)(KEY=EXTPROC1)))
[oracle@PRIM ~]$ dgmgrl
DGMGRL for Linux: Version 10.2.0.1.0 - Production
Copyright (c) 2000, 2005, Oracle. All rights reserved.
Welcome to DGMGRL, type "help" for information.
DGMGRL> connect /
Connected.
DGMGRL> create configuration test as
primary database is PRIM
connect identifier is PRIM
;Configuration "test" created with primary database "prim"
DGMGRL> add database STAN as
connect identifier is STAN
maintained as physical;Database "stan" added
DGMGRL> show configuration
Configuration
Name: test
Enabled: NO
Protection Mode: MaxPerformance
Fast-Start Failover: DISABLED
Databases:
prim - Primary database
stan - Physical standby database
Current status for "test":
DISABLED
DGMGRL> enable configuration
Enabled.
DGMGRL> show configuration
Configuration
Name: test
Enabled: YES
Protection Mode: MaxPerformance
Fast-Start Failover: DISABLED
Databases:
prim - Primary database
stan - Physical standby database
Current status for "test":
Warning: ORA-16607: one or more databases have failed
DGMGRL> show database verbose prim
Database
Name: prim
Role: PRIMARY
Enabled: YES
Intended State: ONLINE
Instance(s):
PRIM
Properties:
InitialConnectIdentifier = 'prim'
LogXptMode = 'ASYNC'
Dependency = ''
DelayMins = '0'
Binding = 'OPTIONAL'
MaxFailure = '0'
MaxConnections = '1'
ReopenSecs = '300'
NetTimeout = '180'
LogShipping = 'ON'
PreferredApplyInstance = ''
ApplyInstanceTimeout = '0'
ApplyParallel = 'AUTO'
StandbyFileManagement = 'AUTO'
ArchiveLagTarget = '0'
LogArchiveMaxProcesses = '30'
LogArchiveMinSucceedDest = '1'
DbFileNameConvert = '/u01/app/oracle/oradata/STAN, /u01/app/oracle/oradata/PRIM'
LogFileNameConvert = '/u01/app/oracle/oradata/STAN, /u01/app/oracle/oradata/PRIM'
FastStartFailoverTarget = ''
StatusReport = '(monitor)'
InconsistentProperties = '(monitor)'
InconsistentLogXptProps = '(monitor)'
SendQEntries = '(monitor)'
LogXptStatus = '(monitor)'
RecvQEntries = '(monitor)'
HostName = 'PRIM'
SidName = 'PRIM'
LocalListenerAddress = '(ADDRESS=(PROTOCOL=tcp)(HOST=PRIM)(PORT=1521))'
StandbyArchiveLocation = '/u01/app/oracle/flash_recovery_area/PRIM/archivelog/'
AlternateLocation = ''
LogArchiveTrace = '0'
LogArchiveFormat = '%t_%s_%r.arc'
LatestLog = '(monitor)'
TopWaitEvents = '(monitor)'
Current status for "prim":
Error: ORA-16778: redo transport error for one or more databases
DGMGRL> show database verbose stan
Database
Name: stan
Role: PHYSICAL STANDBY
Enabled: YES
Intended State: ONLINE
Instance(s):
STAN
Properties:
InitialConnectIdentifier = 'stan'
LogXptMode = 'ASYNC'
Dependency = ''
DelayMins = '0'
Binding = 'OPTIONAL'
MaxFailure = '0'
MaxConnections = '1'
ReopenSecs = '300'
NetTimeout = '180'
LogShipping = 'ON'
PreferredApplyInstance = ''
ApplyInstanceTimeout = '0'
ApplyParallel = 'AUTO'
StandbyFileManagement = 'AUTO'
ArchiveLagTarget = '0'
LogArchiveMaxProcesses = '30'
LogArchiveMinSucceedDest = '1'
DbFileNameConvert = '/u01/app/oracle/oradata/PRIM, /u01/app/oracle/oradata/STAN'
LogFileNameConvert = '/u01/app/oracle/oradata/PRIM, /u01/app/oracle/oradata/STAN'
FastStartFailoverTarget = ''
StatusReport = '(monitor)'
InconsistentProperties = '(monitor)'
InconsistentLogXptProps = '(monitor)'
SendQEntries = '(monitor)'
LogXptStatus = '(monitor)'
RecvQEntries = '(monitor)'
HostName = 'STAND'
SidName = 'STAN'
LocalListenerAddress = '(ADDRESS=(PROTOCOL=tcp)(HOST=STAND)(PORT=1521))'
StandbyArchiveLocation = '/u01/app/oracle/flash_recovery_area/STAN/archivelog/'
AlternateLocation = ''
LogArchiveTrace = '0'
LogArchiveFormat = '%t_%s_%r.arc'
LatestLog = '(monitor)'
TopWaitEvents = '(monitor)'
Current status for "stan":
Error: ORA-12545: Connect failed because target host or object does not exist
DGMGRL>

This:
Current status for "stan":
Error: ORA-12545: Connect failed because target host or object does not exist
says that your network setup is not correct. You need to resolve that first.
As for Broker setup steps how about the doc or our Data Guard 11g Handbook?
It's 3 DGMGRL commands so I am not sure what 'steps' you need?
Larry

See my query and error, see my query and error

hi master
sir i use inner query but not run
please see my query with error
query :==========
select accid as acccode,fstatus, case when fstatus=1 then
(select sum(drbal) from accbal where substr(accbal.accid,1,length(acccode))=acccode)
end what
from chartofacc
error :========
SQL> /
(select sum(drbal) from accbal where substr(accbal.accid,1,length(acccode))=acccode)
ERROR at line 2:
ORA-00904: "ACCCODE": invalid identifier
please sir give me any idea *

Does this column ACCCODE exist in your table accbal?
The columns in the outer query will not be visible in the inner query but the vise versa is true.

Transport error while exporting swf to enterprise

Hi all,
OLD scenario : Server OS : Windows2003, BO XI3.1 Client OS : Windows XP , all BO lcient tools and Xcelsius 2008 ..system works fine in all respects
New Scenario : Server OS upgraded to Windows 2008 with out doing any modifications on the running applicaitions.
All client tools are able to connect to BO Application including designer, deski , importwizrd, webirichclient with EXCEPTION Xelcius 2008.
In Xcelsius 2008 with SP1 --> while tring to export to Business objects platform, upon giving username and password and authenticationi (any) ...waits for 3-4 sec ...pops up " Transport Error : Communication Failure" .... same error while importing also ..application is not getting response from server ...
pls guide ...thnx ..
.kishore

Sorry for delayed update .The Issue is resolved after un-checking auto assign port to CMS and assigning port number manually.

No transport error while consuming WCF service in a REST way

Hi,
Here is a small article on when we usually face No Transport error and how to get rid of it.
I recently worked on a sample application using “app for Office” (New in Visual Studio 11.0)
What is “app for Office”?
An app for Office is basically a webpage that is hosted inside an Office client application. You can use apps to extend the functionality of a document, email message, meeting request, or appointment. Apps
can run in multiple environments and clients, including rich Office desktop clients, Office Web Apps, mobile browsers, and also on-premises and in the cloud.
What can an app for Office do?
An app for Office can do pretty much anything a webpage can do inside the browser, such as the following:
Provide an interactive UI and custom logic through      JavaScript. (Develop UI using HTML and JavaScript)
Use JavaScript frameworks such as jQuery.
Connect to REST endpoints and web services via      HTTP and AJAX.
Run server-side code or logic, if the page is      implemented using a server-side scripting language such as ASP or PHP.
As “app for Office” doesn’t have an option to write server side scripting (unlike code behind or in-line coding feature in ASP.NET/MVC) we will have to go for web service or WCF service and consume the service
using any JavaScript framework like Jquery.
I wrote a simple WCF service to hook up with server side code and consumed the service using Jquery as follows
$(document).ready(function () {
$.ajax({
type: "GET",
url: "http://localhost/MyService.svc/rh/data?id=" + $('#sampleType').val(),
processData: false,
contentType: "application/json; charset=utf-8",
dataType: "json",
crossDomain: true,
success: function (data) {
alert(data)
error: function (xhr, status, error) {
alert(error);
I encountered an error saying “No Transport” when I executed the client application.
I did some investigation on this and found out the root cause that cross-domain request was disabled. But I was really not sure whether it was at my WCF service end or “app for Office” client end. I added
Client Access policy and Cross-domain-policy xml files to WCF service in order to enable cross-domain request
so that service will accept any type requests sent form different domains.
Client Access policy
<?xml version="1.0" encoding="utf-8" ?>
<access-policy>
<cross-domain-access>
<policy>
<allow-from http-request-headers="*">
<domain uri="*"/>
</allow-from>
<grant-to>
<resource include-subpaths="true" path="/"/>
</grant-to>
</policy>
</cross-domain-access>
</access-policy>
Cross-domain-policy
<?xml version="1.0"?>
<!DOCTYPE cross-domain-policy SYSTEM "http://www.macromedia.com/xml/dtds/cross-domain-policy.dtd">
<cross-domain-policy>
<allow-http-request-headers-from domain="*" headers="*"/>
</cross-domain-policy>
Both the policies should be in different XML files
But this didn’t solve my problem. After a little bit more investigation I found exactly where and how to enable-cross domain requests.
Solution
We need to enable cross-domain requests in environments that do not support cross-domain requests.
“Cors is equal to true if a browser can create an XMLHttpRequest object and if thatXMLHttpRequest
object has a withCredentials property. To enable cross-domain requests in environments that do not support cors yet but do allow cross-domain XHRrequests (windows gadget, etc), set $.support.cors = true;”
You just have to add jQuery.support.cors = true; in your client scripting and it works perfectly fine.
[Cors- Cross-Origin Resource Sharing]
A simple example:
$.support.cors = true;
$(document).ready(function () {
$.ajax({
type: "GET",
url: "http://localhost/MyService.svc/rh/data?id=" + $('#sampleType').val(),
processData: false,
contentType: "application/json; charset=utf-8",
dataType: "json",
crossDomain: true,
success: function (data) {
alert(data)
error: function (xhr, status, error) {
alert(error);
Hope this will be helpful.
Thanks

This is very good technich to resolve the problem. but this is not working in Google chrome or Firfox . can any one help me.

Query transport error

Similar Messages

Maybe you are looking for