9.2.0.4 on linux

Have any of you experienced similar problems with XDB while patching or upgrading? Jared Yes. In our case, the XDB tablespace was simply too small. We were not planning on using it, but installed it anyway, and had set the XDB tblspc size to somethin like 32M. We wound up setting autoextend

toad on linux

Hello, It appears that Toad does not run on the Linux desktop, or at least the system requirements mention only Windows platforms. Does any one know of any toad-like tools that do run on Linux? Specifically, Red Hat Linux? The server would be a 9.2.0.4 database also running on Red Hat Linux AS

XDB,Context questions

Hello, We are starting to investigate different methods of searching large medical documents for key words or phrases. The documents may be text, html, xml, or MS word documents. The main idea is to search and retrieve a list of documents quickly that match a given medical key word(s) or

streams comments

Hello, env: Oracle 9.2.0.3 on Solaris. I am looking for any comments, good or bad, regarding Oracle Streams. We are considering using this to transfer data between some 9.2 databases on multiple Sun machines, and hope that someone would share their experience with us. Our rationale for using

RE: Dimensional Modeling - b-t

*** Comments by BECKER, BILL Wed Jun 25, 2003 -- 07:51:18 AM Hi Paula, Oracle offers both a STAR and a STAR_TRANSFORMATION hint, and each results in a different optimizer path. The STAR hint builds a cartesian product across the dimension tables, then joins that virtual table

Migration to 9.2.0.3.0 (64 Bit

*** Comments by BECKER, BILL Fri Jun 20, 2003 -- 08:09:59 AM We upgraded to 64-bit 9.2.0.3.0 on Solaris 9 a few weeks ago, and are currently experiencing ORA-01733 virtual column not allowed here errors - bug 2884797. This is a star transformation bug, and you are likely to hit it if you

daily clone

Hello, Env: Oracle 9.2.0.2.0 on Solaris 9 (2 machines) I'm trying to set up a daily cloning process between 2 Oracle instances (SIDA is source, SIDB is target) using the CREATE CONTROLFILE REUSE SET DATABASE SIDB ... method. The steps are: 1) Shutdown immediate SIDB 2) Shutdown immediate

constraints and optimizer

Hello, Env: Oracle 9.2.0.2.0 on Solaris 9 I suspect this is a foolish question, but I will ask anyway: (It's Friday; my brain stops working after Wednesday) How much does the presence of constraints influence the optimizer, if the indexes are present? We are developing a method for

remota / as sysdba

I have got this working now; I am able to connect remotely using connect sys/[EMAIL PROTECTED] as sysdba and able to do remote imports with sys as the userid. Thanks to the four J's (Jacques,Jared,Julie,Jeremiah) for their suggestions. The solution seems to be dropping and re-creating the

Re: remota / as sysdba

*** Comments by BECKER, BILL Fri Mar 07, 2003 -- 10:56:38 AM No Windows. Env is Oracle Enterprise 9.2.0.2 on Solaris 5.9 (or 2.9 or 9, whatever version number happens to be the version-du-jour) *** Original

remote / as sysdba

Hello, env: Oracle 9.2.0.2 on Solaris 9. Does anyone know of a way to use the / as sysdba logon remotely? (to a separate Oracle instance on a separate machine) Other remote user logons work OK. I have tried several variations from sqlplus, such as [EMAIL PROTECTED]connect /@DWQ as sysdba

RE: remote / as sysdba

*** Comments by BECKER, BILL Thu Mar 06, 2003 -- 03:30:49 PM I have tried this, but it still does not work. [EMAIL PROTECTED]select value from v$parameter 2 where name = 'remote_login_passwordfile'; VALUE

buffer pools

Hello, Env: 9.2.0.2 on Solaris 2.9 We are currently considering a proposal regarding the use of the 3 buffer pools represented by db_cache_size, db_keep_cache_size, and db_recycle_cache_size. I am wondering if this is a good idea or a bad idea. The proposal follows. The buffer pool space can

access/oracle

Hello, We are stuck with a group of users who insist on using MS access 2K 9.0 on a Win2K workstation as an adhoc query front end to an Oracle 8.1.7.4 db on Sun. The problem is that their queries run OK when executed from sqlplus directly against Oracle, but are terrible when executed from

partitioning star schema

Hello, We are still struggling with partitioning of star schema fact tables. As of yet, we haven't been able to test/compare any of the following scenarios (because we're not yet legal with the partitioning option), so I am posting in the hope that someone with more partitioning experience will

partitioning questions

Hello, We are planning to move to Oracle 9.2 on as-yet-undecided platform (probably red hat linux on ibm hardware). We finally pursuaded management to purchase the partitioning license, and I have some questions on partitioning: Scenario: Range-Partition tableA on a service_date field by year;

AIX vs Solaris

Hello, What are the major differences between AIX and Solaris regarding operating system features? We are planning a new machine purchase; currently we are on a Sun machine running Solaris, but IBM is making a strong proposal to management (meaning significantly less cost), and we are wondering

logoff trigger

Hello, We are on 8.1.7.4.0 (on Solaris), and are having a problem with a logoff trigger and ORA-00164: autonomous transaction disallowed within distributed transaction. The logoff trigger is defined as: CREATE OR REPLACE TRIGGER get_logoff_stats_trg BEFORE LOGOFF ON DATABASE BEGIN

kill session

Hello, I received a request from a developer, who is working on a client C++ front end application intended to perform semi-customized queries against a star schema in a datawarehouse. By semi- customized, I mean the fields selected are usually the same, the user can change date ranges, age

DW Setup

Thanks for the response, Don. RichG. also wondered why 2 instances. I should have included the fact these will be running on 2 different platforms as well. Apologies for the omission. Actually, I didn't include that fact because the hardware is still under discussion; we're talking to Sun about

DW setup

Hello, BACKGROUND: We've been planning a 300GB datawarehouse architecture for Oracle 9.2 on Solaris, and have proposed the following: 1) 2 separate instances of Oracle 9.2, - Instance A will be the staging instance, all ETL processing will take place here - Instance B will be the

Re:DW setup

*** Comments by BECKER, BILL Mon Oct 14, 2002 -- 02:24:00 PM Thanks for the response, Don. RichG. also wondered why 2 instances. I should have included the fact these will be running on 2 different platforms as well. Apologies for the confusion. Actually, I didn't include that fact