Strange database behaviour (AXapta, Oracle, 2-tier)

Strange database behaviour (AXapta, Oracle, 2-tier)

Post by UmljaGFyZ » Thu, 04 May 2006 16:42:01


Hi,


My configuration shows strange database behaviour. On the same machine, I
have the following installed:

Oracle Database Server with two databases: Test and Production
Two AXapta installations in separate directories (Test and Production).

I recently copied the database Production to database Test. I now connect
with the Test AXapta to the Test database. But the titlebar of Axapta states:
user@Production

It seems that this problem only occurs in combination with an Oracle
database server.

Anyone else experienced these problems, and/or knows a solution? It's quite
annoying that I can't see the difference between Production and Test
environment.

Thank you in advance,


Richard
 
 
 

Strange database behaviour (AXapta, Oracle, 2-tier)

Post by Asger Wenn » Thu, 04 May 2006 23:36:34

Hi Richard

Did you make sure that you select the proper Axapta Configuration for each
instance?
The most likely reason for your problem is that you still have the
configuration for your production environment active while starting your
test application.

To solve this, make sure you select the proper configuration before starting
the instance. This can be done using a parameter when starting Axapta.

Create shortcuts to each instance, and add the parameter
"-regconfig=configuration_name_goes_here" to the commandline (Target). The
resulting commandline should look similar to this:

"K:\Axapta Client\Bin\ax32.exe" -regconfig=Prod
(assuming the production environment is installed on "K:\" and that the
axapta configuration is called "prod")

or

"K:\AxTest\Axapta Client\Bin\ax32.exe" -regconfig=Test
(assuming the test environment is installed on "K:\AxTest" and that the
axapta configuration is called "test")


Hope this helps.

/Asger

 
 
 

Strange database behaviour (AXapta, Oracle, 2-tier)

Post by UmljaGFyZ » Fri, 05 May 2006 00:39:10

Yes, I did select the right configuration. But instead of using the startup
parameters, I used the Configuration Utility. Always worked fine for me with
Microsoft SQL Server, but not with Oracle.

But thanks for sharing your thoughts about this subject. Hopefully someone
has a solution!

Greetings, Richard
 
 
 

Strange database behaviour (AXapta, Oracle, 2-tier)

Post by UmljaGFyZ » Wed, 10 May 2006 22:45:03

Well, I came one step further in my research, but still no solution :( I
found out that:

1. I connect to the right database (Test)
2. The titlebar text comes from a Class called SysDBInformation
3. This information is also shown in the Form SysSqlStatus. There it states
that currently I'm connected to the Production database (although I connect
to Test)

Is there someone that has the technical background, and can propose me the
solution for this?

TIA, Richard
 
 
 

Strange database behaviour (AXapta, Oracle, 2-tier)

Post by Sm9obiBIdW » Fri, 15 Sep 2006 17:37:01

xapta reads the database's global_name. If you copy the production database
into a new directory and start that up, it will still have it's original
global name.
So you can change it as follows:

Log into as SYS and issue:
ALTER DATABASE RENAME global_name TO "Test";



"Richard" wrote: