Improve company productivity with a Business Account.Sign Up

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 1029
  • Last Modified:

Ending global transaction

Trying to play with Warehouse builder.  When i try logging on i get a message  "API5022 : Cannot connect to specidied repository.  Verify connection information API0322: Internal Error started new global transaction without ending existing global transaction.  How do i end the global transaction?   How do i find out what it is?
0
xoxomos
Asked:
xoxomos
  • 3
  • 2
  • 2
1 Solution
 
p_yaroslavCommented:
Hello!

May be It helps:
_________________________________________
PURPOSE
-------

To inform users of a filed enhancement request for the requested functionality.

 
SCOPE & APPLICATION
-------------------

For all OWB administrators desiring multi-user access to the repository.


ALLOW SHARING OF AN OWB REPOSITORY WITH DIFFERENT DATABASE USERS
-----------------------------
 
An Enhancement Request has been filed for the requested functionality.
BUG:2196724 was filed requesting sharing of the OWB Repository with different
database users.  

Currently, granting a database user access to the OWB repository directly,
via a role, or via synonyms results in the following error when
attempting to connect:
'API5022: Cannot connect to the specified repository. Verify
connection information'

Only the Repository owner can connect.

RELATED DOCUMENTS
-----------------

BUG:2196724 ALLOW SHARING OF AN OWB REPOSITORY WITH DIFFERENT DATABASE USERS
.

 

--------------------------------------------------------------------------------
 
 Copyright (c) 1995,2000 Oracle Corporation. All Rights Reserved. Legal Notices and Terms of Use.
_____________________________________

Best regards,
Yaroslav.
0
 
schwertnerCommented:
Try to analyze the sessions and kill the not needed.

Identify which session to terminate with the
V$SESSION dynamic performance view:
SELECT sid, serial# FROM v$session WHERE
username=‘SCOTT’;

Execute the ALTER SYSTEM command:

ALTER SYSTEM KILL SESSION ‘7,15’;



How to Terminate Sessions
ALTER SYSTEM KILL SESSION ’integer1,integer2’
where: KILL SESSION Identifies the session with both of the
following values from the V$SESSION view:
integer1: value of the SID column
integer2: value of the SERIAL# column
Note: The session ID and serial number are used to uniquely identify a session. This
guarantees that the ALTER SYSTEM command is applied to the correct session even
if the user logs off and a new session uses the same session ID.
Effects of Terminating a Session
The ALTER SYSTEM KILL SESSION command causes the background process
PMON to perform the following steps upon execution:
• Roll back the user’s current transaction
• Release all currently held table or row locks
• Free all resources currently reserved by the user
0
 
xoxomosAuthor Commented:
I try the select
SELECT sid, serial# FROM v$session
Get a list of sessions, then
ALTER SYSTEM KILL SESSION ‘7,15’;
then SELECT sid, serial# FROM v$session  again.
The list comes out the same.  I've even tried commit after the ALTER SYSTEM.  Is there something missing?



0
Free Tool: Site Down Detector

Helpful to verify reports of your own downtime, or to double check a downed website you are trying to access.

One of a set of tools we are providing to everyone as a way of saying thank you for being a part of the community.

 
xoxomosAuthor Commented:
Embarassing!  I had done the repository and runtime on a different machine!  Still if you could explain why after issuing the kill sessions, they still show, it'll be worth it.
0
 
schwertnerCommented:
I am also confused. Check every detail of your configuration to figure out where the components of your installation are. Define the real target of your action.
0
 
schwertnerCommented:
I am also confused. Check every detail of your configuration to figure out where the components of your installation are. Define the real target of your action.
0
 
p_yaroslavCommented:
Hi!

After kill session they may be still show for a time (till transaction finish). It's Ok! After transaction finishes they are disappear.

After kill session trey:
select status from v$session
where serial#=<sn> and sid=<sid>;

It must be "killed".

Best regards,
Yaroslav.
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

Join & Write a Comment

Featured Post

Free Tool: Path Explorer

An intuitive utility to help find the CSS path to UI elements on a webpage. These paths are used frequently in a variety of front-end development and QA automation tasks.

One of a set of tools we're offering as a way of saying thank you for being a part of the community.

  • 3
  • 2
  • 2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now