Solaris 9 x86 bug report - el_GR.ISO8859-7 & CDE

I'm posting this article here, because I can't find any official Solaris 9 x86 bug report page. I hope the developers will notice it. I'm using Solaris 9 x86 (12/02), with the latest 9_x86_Recommended patch cluster installed, and support for Greek installed too.
It seems there is some kind of problem, when trying to view text files with Greek (el_GR.ISO8859-7) characters, which were created under Windows. To be more specific:
If I boot at CDE with language el_GR.ISO8859-7, and try to view a .txt file (just with a simple double click), which I have created under Windows, with Greek characters,
the screen goes black, and the CDE login screen appears again (restarts). If I keep the Greek language or change the language to US English, I can boot at CDE again, with
no problems. If I try "command line logging", the screen goes off - just like when the computer is powered off, and I can't do anything, (well, except pressing the reset button, that's the sure way). And if I use the "init 6" command, while being logged at CDE, from a terminal, the Graphical Desktop exits, and then, the screen goes off again (just like the computer is powered off), but finally the computer manages to restart.
I'm using the Sun X server, NOT the XFree86 porting kit and I use the entry
:0 Local local_uid@console nobody /usr/openwin/bin/Xsun :0 -dpsfileops
in /usr/dt/config/Xservers file, to start the X server.
Here is the $HOME_DIR/.dt/startlog file:
--- ??? 23 ??? 2003 12:10:51
--- /usr/dt/bin/Xsession starting...
--- starting /usr/openwin/bin/speckeysd
--- Xsession started by dtlogin
--- starting /usr/dt/bin/dtsession_res -load -system
--- sourcing /root/.dtprofile...
--- sourcing /usr/dt/config/Xsession.d/0010.dtpaths...
--- sourcing /usr/dt/config/Xsession.d/0015.sun.env...
--- sourcing /usr/dt/config/Xsession.d/0020.dtims...
--- sourcing /usr/dt/config/Xsession.d/0030.dttmpdir...
--- sourcing /usr/dt/config/Xsession.d/0040.xmbind...
--- sourcing /usr/dt/config/Xsession.d/1000.solregis...
--- could not read /root/.profile
--- starting /usr/dt/bin/dthello &
--- starting /usr/dt/bin/dtsearchpath
--- starting /usr/dt/bin/dtappgather &
--- starting /usr/dt/bin/dsdm &
--- session log file is /root/.dt/sessionlogs/www_DISPLAY=:0
--- DTSOURCEPROFILE is 'true' (see /root/.dtprofile)
--- execing /usr/dt/bin/dtsession with a /sbin/sh login shell ...
--- starting desktop on /dev/pts/3
Sun Microsystems Inc. SunOS 5.9 Generic_112234-03 November 2002
/usr/dt/bin/ttsession[337]: starting
X connection to :0.0 broken (explicit kill or server shutdown).
X connection to :0.0 broken (explicit kill or server shutdown).
I don't know if this is a bug or something, and I'm very curious about the cause. I didn't have much time for any other "experiments".
Anyway, I hope this will help developers solve a problem -if it really exists-.
Angelos Vasilopoulos
Site Security Officer
[email protected]

Similar Messages

F90 bug on solaris x86

Hello,
I have a short code to show a curious bug on solaris x86 when i compil it with f90 -O3.
Where can i send it to show this bug ?
Thanks

The bug ID for this problem is 6413443. It has been fixed in both the development release and the patch release. Fix should be available in the upcoming patches for Studio 11 and in the next release of Sun Studio Express - SSX3.
Best regards,
Boris

Solaris8 and 9 (possibly 7) /dev/poll driver bug report.

Hello,
I'd like to report a bug in the solaris 8 and 9 /dev/poll driver (poll(7d)).
As i do not have a support account with sun or anything like that, there
seems to be no other way to do that here (which is of course a very sad
thing).
Bug details:
The /dev/poll device provides an ioctl-request (DP_ISPOLLED) for checking
if a particular filedescriptor is currently in the set of monitored
filedescriptors for that particular /dev/poll fd set (open /dev/poll fd).
A quote from the documentation of the poll(7d) manual page taken from
Solaris9:
"DP_ISPOLLED ioctl allows you to query if a file descriptor is already in
the monitored set represented by fd. The fd field of the pollfd structure
indicates the file descriptor of interest. The DP_ISPOLLED ioctl returns 1
if the file descriptor is in the set. The events field contains the
currently polled events. The revents field contains 0. The ioctl returns 0
if the file descriptor is not in the set. The pollfd structure pointed by
pfd is not modified. The ioctl returns a -1 if the call fails."
It says that when you query for an filedescriptor which is currently being
monitored in the set, that it would return 1, and change the events field of
the pollfd structure to the events it's currently monitoring that fd for.
The revents field would be set to zero.
However the only thing which actually happens here, is that FD_ISPOLLED
returns 1 when the fd is in the set and 0 if not. When the fd is in the
set, when FD_ISPOLLED returns 1, the events field remains unmodified, but
the revents field gets changed.
A small sample code to illustrate:
#include <stdio.h>
#include <unistd.h>
#include <sys/types.h>
#include <sys/stat.h>
#include <fcntl.h>
#include <sys/devpoll.h>
main() {
struct pollfd a;
int dp_fd = open("/dev/poll", O_WRONLY);
a.fd = 0; /* stdin */
a.events = POLLIN; /* we monitor for readability, POLLIN=1 */
a.revents = 0;
write(dp_fd, &a, sizeof(a));
a.fd = 0;
a.events = 34; /* filled in with bogus number to show malfunctioning */
a.revents = 0;
printf("DP_ISPOLLED returns: %d\n", ioctl(dp_fd, DP_ISPOLLED, &a));
printf("a.fd=%d, a.events=%hd, a.revents=%hd\n", a.fd, a.events,
a.revents);
According to the documentation of /dev/poll and namely DP_ISPOLLED this
program is supposed to print the following:
DP_ISPOLLED returns: 1
a.fd=0, a.events=1, a.revents=0
However it prints the following:
DP_ISPOLLED returns: 1
a.fd=0, a.events=34, a.revents=1
You can take any number instead of '34' and it will simply remain untouched
after the DP_ISPOLLED ioctl-request.
I hope it's clear now that the solaris8 and solaris9 (and probably solaris7
with /dev/poll patch too) DP_ISPOLLED implementation is broken.
This bug is also easily illustrated by looking at the solaris8 kernel sourcecode:
<snippet osnet_volume/usr/src/uts/common/io/devpoll.c:dpioctl()>
case DP_ISPOLLED:
pollfd_t pollfd;
polldat_t *pdp;
if (pollfd.fd < 0) {
mutex_exit(&pcp->pc_lock);
break;
pdp = pcache_lookup_fd(pcp, pollfd.fd);
if ((pdp != NULL) && (pdp->pd_fd == pollfd.fd) &&
(pdp->pd_fp != NULL)) {
pollfd.revents = pdp->pd_events;
if (copyout(&pollfd, (caddr_t)arg,
sizeof(pollfd_t))) {
mutex_exit(&pcp->pc_lock);
DP_REFRELE(dpep);
return (set_errno(EFAULT));
*rvalp = 1;
</snippet>
its' clearly visible that the code writes the current monitored events to
the revents field:
'pollfd.revents = pdp->pd_events;'
and that it doesnt set revents to zero.
It's funny to see that this has been like this since Solaris8 (possibly 7). That means nobody ever used DP_ISPOLLED that way or people were simply to lazy to file a bug report.
Another funny thing related to this. is that Hewlett-Packard did seem to know about this. Since HP-UX11i version 1.6 they also support /dev/poll. From their manual page i ll quote some sentences from their WARNING session:
"The ioctl(DP_ISPOLLED) system call also returns its result in the revents member of the pollfd structure, in order to be compatible with the implementation of the /dev/poll driver by some other vendors."
Hopefully this will get fixed.
I also like to reexpress my very negative feelings towards the fact that you're not able to file bug reports when you do not have a support contract. Ridiculous.
Thanks,
bighawk

Have I mentioned how much i love my playbook now Great job on os 2.0

Mounting a Solaris x86 CD/DVD from a remote Windows CD/DVD-ROM drive

Greetings, all.
Is it possible to mount a remote Windows CD/DVD-ROM drive? I have the Solaris 10x86 Companion Software DVD sitting in a CD/DVD-ROM drive that's installed on a Windows server on my network. It is shared-out (F:) and the two servers can ping each other. I've also confirmed the NFS services/daemons are running on the Solaris x86 machine. I've tried the following variations but, all have failed to produce successful results:
# mount -F nfs x.x.x.x:/f /mnt
nfs mount: x.x.x.x: : RPC: Program not registered
nfs mount: retrying: /mnt
# mount -F hsfs x.x.x.x:/f /mnt
mount: No such device
mount: cannot mount x.x.x.x:/f
# mount -F hsfs x.x.x.x:/F /mnt
mount: No such device
mount: cannot mount x.x.x.x:/F
[FYI: S10_106_SOFTWARE is the DVD's label as reported by Windows Explorer.]
# mount -F hsfs x.x.x.x:/S10_106_SOFTWARE /mnt
mount: No such device
mount: cannot mount x.x.x.x:/S10_106_SOFTWARE
# mount -F hsfs x.x.x.x:/s10_106_software /mnt
mount: No such device
mount: cannot mount x.x.x.x:/s10_106_software
# mount -F nfs x.x.x.x:/S10_106_SOFTWARE /mnt
nfs mount: x.x.x.x: : RPC: Program not registered
nfs mount: retrying: /mnt
# mount -F nfs x.x.x.x:/s10_106_software /mnt
nfs mount: x.x.x.x: : RPC: Program not registered
nfs mount: retrying: /mnt
# mount -F hsfs x.x.x.x:/f/s10_106_software /mnt
mount: No such device
mount: cannot mount x.x.x.x:/f/s10_106_software
# mount -F hsfs x.x.x.x:/F/s10_106_software /mnt
mount: No such device
mount: cannot mount x.x.x.x:/F/s10_106_software
# mount -F hsfs x.x.x.x:/f/S10_106_SOFTWARE /mnt
mount: No such device
mount: cannot mount x.x.x.x:/f/S10_106_SOFTWARE
# mount -F hsfs x.x.x.x:/F/S10_106_SOFTWARE /mnt
mount: No such device
mount: cannot mount x.x.x.x:/F/S10_106_SOFTWARE
I've also tried mounting it at bootup by adding the appropriate entry in the /etc/vfstab file but, this does not work as well. I've tried Google'ing for an answer to my issue but, I haven't been able to find anything that applies directly to what I'm reporting. It's usually chatter about mounting from one UNIX server to another. Any advice from the community would be greatly appreciated.

After three weeks, you deserve a reply. Windoze does
not natively support NFS.Also deserves a decent answer...
There are two ways to do this:
Install Microsoft's free "Windows Services for UNIX," which includes a Windows NFS server; or
Install the 'sharity' package (google for it); it provides Solaris systems the ability to mount Windows shares

Solaris x86 or Solaris 8

What is the latest version of solaris on intel called? Is it generic
across intel boards? Are there some pitfalls to look out for (i.e.
only runs on 400 MHz or less, only a handfull of graphic cards, etc.)
What is the best C/C++ compiler? Does it support Visual Workshop?
How about Motif? What version? We were using Motif 1.2.4 on X11R5
from ICS, is this OK? Any heads up would be helpful. Thanks in advance.

Solaris 8 is currently available at
http://www.sun.com/software/solaris/binaries/index.html
Not sure what you mean by "generic across intel boards" - it's the
same kernel, but drivers will differ depending on your H/W config -
see the HArdware Compatibility list:
http://soldc.sun.com/support/drivers/hcl/index.html
There are freeware e.g. GNU compilers - go to sunfreeware.com
For serious commercial development, the Sun Workshop tools are
available - Workshop 5 is shipping now and you can get a WS6 early access at the access1.sun.com website.
CDE seems to have taken over from Motif. For details on X11R6 features etc, follow the first link below:
- www.sun.com/solaris
- www.sun.com/intel (For Solaris on the Intel Platform)
- www.sunfreeware.com (take a look at the "Other Useful Sites")
- www.egroups.com (do a search on Solaris, many questions already answered)
- Newsgroups (alt.solaris.x86, comp.unix.solaris)
- www.webring.org/cgi-bin/webring?ring=solarisunix;list
- www.SolarisCentral.org
- metalab.unc.edu/pub/packages/solaris/i86pc/
- http://solarisguide.com
- dan.carlsbad.ca.us/faqs/s86faq.html
- solarisguide.com
- http://fishbutt.fiver.net
- http://www.sunhelp.org/

BUG REPORT: new 10g Driver throws SQLExcpetion

So far, i just replaced my old ORACLE JDBC driver jar file with a new version. Of course, i use the classes12.jar to be used by JDK 1.3. This worked for all the 9.xxx Drivers. Now, i tried to use the classes12.jar from the new "10g" Driver (10.1.0.2.0) but it doesn't work anymore. The first simple SELECT statement throws this error:
java.sql.SQLException: Typlänge größer als Höchstwert
     at oracle.jdbc.driver.DatabaseError.throwSqlException(DatabaseError.java:124)
     at oracle.jdbc.driver.DatabaseError.throwSqlException(DatabaseError.java:161)
     at oracle.jdbc.driver.DatabaseError.check_error(DatabaseError.java:884)
     at oracle.jdbc.driver.T4CMAREngine.buffer2Value(T4CMAREngine.java:2230)
     at oracle.jdbc.driver.T4CMAREngine.unmarshalUB2(T4CMAREngine.java:1047)
     at oracle.jdbc.driver.T4CTTIdcb.receiveCommon(T4CTTIdcb.java:111)
     at oracle.jdbc.driver.T4CTTIdcb.receive(T4CTTIdcb.java:94)
     at oracle.jdbc.driver.T4C8Oall.receive(T4C8Oall.java:590)
     at oracle.jdbc.driver.T4CStatement.doOall8(T4CStatement.java:111)
     at oracle.jdbc.driver.T4CStatement.execute_for_describe(T4CStatement.java:350)
     at oracle.jdbc.driver.OracleStatement.execute_maybe_describe(OracleStatement.java:895)
     at oracle.jdbc.driver.T4CStatement.execute_maybe_describe(T4CStatement.java:382)
     at oracle.jdbc.driver.OracleStatement.doExecuteWithTimeout(OracleStatement.java:985)
     at oracle.jdbc.driver.OracleStatement.executeQuery(OracleStatement.java:1124)
For the simple select statement:
select REF_CLASS, REF_CODE, REF_TEXT_DE from refset order by REF_CLASS,REF_CODE
so, nothing special. Going back to the last 9.x driver, it works again. Is the 10g driver knwon to be buggy?
Is there an official bug report web page on the ORACLE site (similar to the sun Java bug database)?

Hi all,
I am seeing following exception while using Oracle 10.2.0.3 base release with WebSphere 6.1.0.9.
------Start of DE processing------ = [2/3/08 12:59:14:698 CST] , key = java.sql.SQLException com.ibm.ws.rsadapter.jdbc.WSJdbcStatement.pmiExecuteQuery 1315
Exception = java.sql.SQLException
Source = com.ibm.ws.rsadapter.jdbc.WSJdbcStatement.pmiExecuteQuery
probeid = 1315
Stack Dump = java.sql.SQLException: ORA-00942: table or view does not exist
     at oracle.jdbc.driver.DatabaseError.throwSqlException(DatabaseError.java:112)
     at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:331)
     at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:288)
     at oracle.jdbc.driver.T4C8Oall.receive(T4C8Oall.java:745)
     at oracle.jdbc.driver.T4CStatement.doOall8(T4CStatement.java:207)
     at oracle.jdbc.driver.T4CStatement.executeForDescribe(T4CStatement.java:801)
     at oracle.jdbc.driver.OracleStatement.executeMaybeDescribe(OracleStatement.java:1039)
     at oracle.jdbc.driver.T4CStatement.executeMaybeDescribe(T4CStatement.java:841)
     at oracle.jdbc.driver.OracleStatement.doExecuteWithTimeout(OracleStatement.java:1134)
     at oracle.jdbc.driver.OracleStatement.executeQuery(OracleStatement.java:1274)
     at com.ibm.ws.rsadapter.jdbc.WSJdbcStatement.pmiExecuteQuery(WSJdbcStatement.java:1381)
     at com.ibm.ws.rsadapter.jdbc.WSJdbcStatement.executeQuery(WSJdbcStatement.java:754)
     at com.filenet.engine.dbpersist.DBContext.determineDatabaseType(DBContext.java:418)
     at com.filenet.engine.context.ServerCallContext._getDBContext(ServerCallContext.java:611)
     at com.filenet.engine.context.ServerCallContext.getDBContextFromJNDIValues(ServerCallContext.java:783)
     at com.filenet.engine.dbpersist.DBContext.determineDatabaseType(DBContext.java:380)
     at com.filenet.engine.gcd.GCDDBPersistence.<init>(GCDDBPersistence.java:135)
     at com.filenet.engine.gcd.GCDPersistence.getGCDPersistence(GCDPersistence.java:171)
     at com.filenet.engine.gcd.GCD.initialize(GCD.java:226)
     at com.filenet.engine.gcd.GCD.domainAvailable(GCD.java:183)
     at com.filenet.engine.gcd.GCD.isDomainAvailable(GCD.java:119)
     at com.filenet.engine.gcd.GCD.getContextInfo(GCD.java:142)
     at com.filenet.engine.init.StartupUtility.start(StartupUtility.java:136)
     at com.filenet.engine.init.StartupUtility.access$000(StartupUtility.java:39)
     at com.filenet.engine.init.StartupUtility$1.run(StartupUtility.java:68)
     at java.security.AccessController.doPrivileged(AccessController.java:274)
     at javax.security.auth.Subject.doAs(Subject.java:573)
     at com.ibm.websphere.security.auth.WSSubject.doAs(WSSubject.java:168)
     at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
     at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:64)
     at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
     at java.lang.reflect.Method.invoke(Method.java:615)
     at com.filenet.apiimpl.util.J2EEUtilWS.doAs(J2EEUtilWS.java:207)
     at com.filenet.engine.context.CallState.doAsSystem(CallState.java:385)
     at com.filenet.engine.init.StartupUtility.startASSystem(StartupUtility.java:63)
     at com.filenet.engine.jca.impl.ConnectionFactoryImpl.start(ConnectionFactoryImpl.java:120)
     at engine.EngineInit._init(EngineInit.java:60)
     at engine.EngineInit.init(EngineInit.java:132)
     at javax.servlet.GenericServlet.init(GenericServlet.java:256)
     at com.ibm.ws.webcontainer.servlet.ServletWrapper.init(ServletWrapper.java:190)
     at com.ibm.ws.wswebcontainer.servlet.ServletWrapper.init(ServletWrapper.java:317)
     at com.ibm.ws.webcontainer.servlet.ServletWrapper.initialize(ServletWrapper.java:1142)
     at com.ibm.ws.wswebcontainer.servlet.ServletWrapper.initialize(ServletWrapper.java:150)
     at com.ibm.wsspi.webcontainer.extension.WebExtensionProcessor.createServletWrapper(WebExtensionProcessor.java:99)
     at com.ibm.ws.webcontainer.webapp.WebApp.getServletWrapper(WebApp.java:787)
     at com.ibm.ws.webcontainer.webapp.WebApp.initializeTargetMappings(WebApp.java:467)
     at com.ibm.ws.webcontainer.webapp.WebApp.commonInitializationFinish(WebApp.java:304)
     at com.ibm.ws.wswebcontainer.webapp.WebApp.initialize(WebApp.java:285)
     at com.ibm.ws.wswebcontainer.webapp.WebGroup.addWebApplication(WebGroup.java:88)
     at com.ibm.ws.wswebcontainer.VirtualHost.addWebApplication(VirtualHost.java:157)
     at com.ibm.ws.wswebcontainer.WebContainer.addWebApp(WebContainer.java:655)
     at com.ibm.ws.wswebcontainer.WebContainer.addWebApplication(WebContainer.java:608)
     at com.ibm.ws.webcontainer.component.WebContainerImpl.install(WebContainerImpl.java:335)
     at com.ibm.ws.webcontainer.component.WebContainerImpl.start(WebContainerImpl.java:551)
     at com.ibm.ws.runtime.component.ApplicationMgrImpl.start(ApplicationMgrImpl.java:1312)
     at com.ibm.ws.runtime.component.DeployedApplicationImpl.fireDeployedObjectStart(DeployedApplicationImpl.java:1129)
     at com.ibm.ws.runtime.component.DeployedModuleImpl.start(DeployedModuleImpl.java:569)
     at com.ibm.ws.runtime.component.DeployedApplicationImpl.start(DeployedApplicationImpl.java:814)
     at com.ibm.ws.runtime.component.ApplicationMgrImpl.startApplication(ApplicationMgrImpl.java:965)
     at com.ibm.ws.runtime.component.ApplicationMgrImpl$AppInitializer.run(ApplicationMgrImpl.java:2131)
     at com.ibm.wsspi.runtime.component.WsComponentImpl$_AsynchInitializer.run(WsComponentImpl.java:341)
     at com.ibm.ws.util.ThreadPool$Worker.run(ThreadPool.java:1469)
Dump of callerThis =
Object type = com.ibm.ws.rsadapter.jdbc.WSJdbcStatement
First Failure Data Capture information for
com.ibm.ws.rsadapter.jdbc.WSJdbcStatement@53385338
Displaying FFDC information for wrapper hierarchy,
beginning from the Connection...
First Failure Data Capture information for
com.ibm.ws.rsadapter.jdbc.WSJdbcConnection@7c9e7c9e
com.ibm.ws.rsadapter.jdbc.WSJdbcConnection@7c9e7c9e
Transaction Manager global transaction status is
STATUS NO TRANSACTION (6)
Underlying Connection: oracle.jdbc.driver.LogicalConnection@3dfc3dfc
oracle.jdbc.driver.LogicalConnection@3dfc3dfc
Key Object:
[B@14f414f4
DataStoreHelper:
com.ibm.websphere.rsadapter.Oracle10gDataStoreHelper@3ebc3ebc
Connection Manager:
[ConnectionManager]@4ee24ee2
JNDI Name <FNGCDDS>
shareable <true>
ConnectionManager supports lazy association?
true
ConnectionManager supports lazy enlistment?
true
Handle is reserved? false
AutoCommit value tracked by handle: true
Detection of multithreaded access is:
DISABLED
Thread id:
null
Wrapper State:
ACTIVE
Parent wrapper:
null
Child wrapper:
null
# of Child Wrappers 1
Child wrappers:
com.ibm.ws.rsadapter.jdbc.WSJdbcStatement@53385338
ConnectionRequestInfo:
null
First Failure Data Capture information for
com.ibm.ws.rsadapter.spi.WSManagedConnectionFactoryImpl@63666366
Detection of multithreaded access is
DISABLED
Resource Adapter:
null
Hash Code:
-1131425938 (0xbc8fcf6e)
DataSource properties:
{enable2Phase=false, serverName=localhost, statementCacheSize=10, user=gcduser, dataStoreHelperClass=com.ibm.websphere.rsadapter.Oracle10gDataStoreHelper, URL=jdbc:oracle:thin:@localhost:1521:orcl, databaseName=orcl, selectMethod=direct, dataSourceClass=oracle.jdbc.pool.OracleConnectionPoolDataSource, password=******, portNumber=1521}
Database Type:
null
DataStoreHelper:
com.ibm.websphere.rsadapter.Oracle10gDataStoreHelper@3ebc3ebc
Description:
null
InternalDataStoreHelper:
[email protected]8
Log Writer:
null
Performance Monitoring Instrumentation:
com.ibm.ws.pmi.server.modules.J2CModule@46cc46cc
Statement Cache Size (maximum):
10
Transaction Branches are set to be Loosely Coupled:
false
Counter of fatal connection errors on ManagedConnections created by this MCF:
0
Validate existing connections on cleanup after a fatal connection error is detected?
true
ResetConnectionByBackendDatabase:
false
Backend id checking is:
true
JMSOnePhaseOptimization:
false
Reauthentication:
false
newDBConnectionValidationEnabled:
false
connectionRetriesDuringDBFailover:
100
connRetryDurationDuringDBFailover:
3000
Connection Factory Type:
com.ibm.ws.rsadapter.jdbc.WSJdbcDataSource
Listing PropertyChangeListeners:
First Failure Data Capture information for
com.ibm.ws.rsadapter.spi.WSRdbDataSource@34003400
DataSource Implementation Class Name:
oracle.jdbc.pool.OracleConnectionPoolDataSource
DataSource Name:
null
DataStoreHelper:
com.ibm.websphere.rsadapter.Oracle10gDataStoreHelper@3ebc3ebc
DataSource properties:
{enable2Phase=false, serverName=localhost, statementCacheSize=10, user=gcduser, dataStoreHelperClass=com.ibm.websphere.rsadapter.Oracle10gDataStoreHelper, URL=jdbc:oracle:thin:@localhost:1521:orcl, databaseName=orcl, selectMethod=direct, dataSourceClass=oracle.jdbc.pool.OracleConnectionPoolDataSource, password=******, portNumber=1521}
ONE PHASE ENABLED
Underlying DataSource Object: oracle.jdbc.pool.OracleConnectionPoolDataSource@39703970
oracle.jdbc.pool.OracleConnectionPoolDataSource@39703970
Counter of unique, modified DataSource configurations: 0
DynamicDSConfigManager
null
First Failure Data Capture information for
com.ibm.ws.rsadapter.spi.WSRdbManagedConnectionImpl@3f023f02
ONE PHASE ENABLED
Database Type:
null
Transaction State:
NO_TRANSACTION_ACTIVE
Statement Cache Size (maximum):
10
Key:
[B@14f414f4
Performance Monitoring Instrumentation:
com.ibm.ws.pmi.server.modules.J2CModule@46cc46cc
Log Writer:
null
Subject:
null
ManagedConnection:
WSRdbManagedConnectionImpl@3f023f02
Counter of fatal connection errors for the ManagedConnectionFactory as of the most recent getConnection on this ManagedConnection:
0
Default AutoCommit:
true
Current AutoCommit:
true
AutoCommit reported by the JDBC driver:
true
Current Isolation:
READ COMMITTED (2)
Isolation level has changed? :
false
Support isolation level switching:
false
Isolation reported by the JDBC driver:
READ COMMITTED (2)
Catalog, IsReadOnly, or TypeMap has changed? :
false
Default Holdability:
DEFAULT CURSOR HOLDABILITY VALUE (0)
Current Holdability:
DEFAULT CURSOR HOLDABILITY VALUE (0)
Holdability value has changed? :
false
Holdability reported by the JDBC driver:
DEFAULT CURSOR HOLDABILITY VALUE (0)
Thread ID:
null
Lazily enlisted in the current transaction? :
false
Underlying Connection Object: oracle.jdbc.driver.LogicalConnection@3dfc3dfc
oracle.jdbc.driver.LogicalConnection@3dfc3dfc
Underlying PooledConnection Object: oracle.jdbc.pool.OraclePooledConnection@64ec64ec
oracle.jdbc.pool.OraclePooledConnection@64ec64ec
SQLJ Default Context: null
null
Is statement caching enabled? :
true
Fatal connection error was detected? :
false
Currently cleaning up handles? :
false
Last ConnectionEvent sent for this ManagedConnection:
com.ibm.ws.rsadapter.spi.WSConnectionEvent@3f583f58
Connection Handle: null
Event ID: UNKNOWN CONNECTION EVENT CONSTANT (0)
Exception: null
Driver version:
10.2.0.3.0
Database version:
Oracle Database 10g Enterprise Edition Release 10.2.0.3.0 - Production
With the Partitioning, OLAP and Data Mining options
Connection Event Listeners:
com.ibm.ejs.j2c.ConnectionEventListener@6f306f30
Interaction Metrics:
com.ibm.ejs.j2c.ConnectionEventListener@6f306f30
Maximum Handle List Size: 15
Handle Count: 1
Handles:
com.ibm.ws.rsadapter.jdbc.WSJdbcConnection@7c9e7c9e
null
null
null
null
null
null
null
null
null
null
null
null
null
null
State Manager:
com.ibm.ws.rsadapter.spi.WSStateManager@6ec46ec4
XA Resource:
null
First Failure Data Capture information for
com.ibm.ws.rsadapter.spi.WSRdbSpiLocalTransactionImpl@7c827c82
Connection:
oracle.jdbc.driver.LogicalConnection@3dfc3dfc
ManagedConnection:
WSRdbManagedConnectionImpl@3f023f02
Detection of multithreaded access is:
DISABLED
ManagedConnectionMetaData:
null
Statement Cache:
com.ibm.ws.rsadapter.spi.CacheMap@6d486d48
Number of entries: 0
Maximum entries: 10
Number of buckets: 13
Maximum bucket size: 5
Number of discards: 0
BUCKET SIZE PREV NEXT
000 000 013 013
001 000 013 013
002 000 013 013
003 000 013 013
004 000 013 013
005 000 013 013
006 000 013 013
007 000 013 013
008 000 013 013
009 000 013 013
010 000 013 013
011 000 013 013
012 000 013 013
013 LRU 014
014 MRU 013
First Failure Data Capture information for
com.ibm.ws.rsadapter.spi.WSConnectionRequestInfoImpl@345e345e
extention DS properties =
null
extention DS properties key =
0
useHetrogeneous =
false
changable CRI =
false
optimizeForGetUseCloseUsage =
false
User Name:
null
Password:
null
Isolation Level:
READ COMMITTED (2)
Catalog:
null
Is Read Only?
null
Type Map:
null
Cursor Holdability:
DEFAULT CURSOR HOLDABILITY VALUE (0)
Config ID: 0
Hash Code:
0
Support isolation switching on connection:
false
NoEnlistment:
false
ShareWithCMPOnly:
false
Handle type:
java.sql.Connection
TrustedContext_name:
null
TrustedContext_realm:
null
TrustedContext_userSecToken:
null
TrustedContext_originalUser:
null
trustedContextIdentityAttributesAreSet =
false
First Failure Data Capture information for
com.ibm.ws.rsadapter.spi.WSManagedConnectionFactoryImpl@63666366
Detection of multithreaded access is
DISABLED
Resource Adapter:
null
Hash Code:
-1131425938 (0xbc8fcf6e)
DataSource properties:
{enable2Phase=false, serverName=localhost, statementCacheSize=10, user=gcduser, dataStoreHelperClass=com.ibm.websphere.rsadapter.Oracle10gDataStoreHelper, URL=jdbc:oracle:thin:@localhost:1521:orcl, databaseName=orcl, selectMethod=direct, dataSourceClass=oracle.jdbc.pool.OracleConnectionPoolDataSource, password=******, portNumber=1521}
Database Type:
null
DataStoreHelper:
com.ibm.websphere.rsadapter.Oracle10gDataStoreHelper@3ebc3ebc
Description:
null
InternalDataStoreHelper:
[email protected]8
Log Writer:
null
Performance Monitoring Instrumentation:
com.ibm.ws.pmi.server.modules.J2CModule@46cc46cc
Statement Cache Size (maximum):
10
Transaction Branches are set to be Loosely Coupled:
false
Counter of fatal connection errors on ManagedConnections created by this MCF:
0
Validate existing connections on cleanup after a fatal connection error is detected?
true
ResetConnectionByBackendDatabase:
false
Backend id checking is:
true
JMSOnePhaseOptimization:
false
Reauthentication:
false
newDBConnectionValidationEnabled:
false
connectionRetriesDuringDBFailover:
100
connRetryDurationDuringDBFailover:
3000
Connection Factory Type:
com.ibm.ws.rsadapter.jdbc.WSJdbcDataSource
Listing PropertyChangeListeners:
First Failure Data Capture information for
com.ibm.ws.rsadapter.spi.WSRdbDataSource@34003400
DataSource Implementation Class Name:
oracle.jdbc.pool.OracleConnectionPoolDataSource
DataSource Name:
null
DataStoreHelper:
com.ibm.websphere.rsadapter.Oracle10gDataStoreHelper@3ebc3ebc
DataSource properties:
{enable2Phase=false, serverName=localhost, statementCacheSize=10, user=gcduser, dataStoreHelperClass=com.ibm.websphere.rsadapter.Oracle10gDataStoreHelper, URL=jdbc:oracle:thin:@localhost:1521:orcl, databaseName=orcl, selectMethod=direct, dataSourceClass=oracle.jdbc.pool.OracleConnectionPoolDataSource, password=******, portNumber=1521}
ONE PHASE ENABLED
Underlying DataSource Object: oracle.jdbc.pool.OracleConnectionPoolDataSource@39703970
oracle.jdbc.pool.OracleConnectionPoolDataSource@39703970
Counter of unique, modified DataSource configurations: 0
DynamicDSConfigManager
null
==> Performing default dump from com.ibm.ws.rsadapter.DiagnosticModuleForAdapter = Sun Feb 03 12:59:15 CST 2008
This is a FFDC log generated for the Default Resource Adapter from source = com.ibm.ws.rsadapter.jdbc.WSJdbcStatement.pmiExecuteQuery
The exception caught = java.sql.SQLException: ORA-00942: table or view does not exist
SQL Error Code is 942 SQL State is = 42000
Operating System = Windows Server 2003 5.2 build 3790 Service Pack 2 x86
Classpath = C:\Program Files\IBM\WebSphere\AppServ\profiles\AppSrv02/properties;C:/Program Files/IBM/WebSphere/AppServ/properties;C:/Program Files/IBM/WebSphere/AppServ/lib/startup.jar;C:/Program Files/IBM/WebSphere/AppServ/lib/bootstrap.jar;C:/Program Files/IBM/WebSphere/AppServ/lib/j2ee.jar;C:/Program Files/IBM/WebSphere/AppServ/lib/lmproxy.jar;C:/Program Files/IBM/WebSphere/AppServ/lib/urlprotocols.jar;C:/Program Files/IBM/WebSphere/AppServ/deploytool/itp/batchboot.jar;C:/Program Files/IBM/WebSphere/AppServ/deploytool/itp/batch2.jar;C:/Program Files/IBM/WebSphere/AppServ/java/lib/tools.jar
Ext dirs = C:\Program Files\IBM\WebSphere\AppServ\java\jre\lib\ext
Other related data. If null, nothing was passed in =
null
The Objects' instance variables are printed below recursively 2 levels deep =
Object type = com.ibm.ws.rsadapter.jdbc.WSJdbcStatement
First Failure Data Capture information for
com.ibm.ws.rsadapter.jdbc.WSJdbcStatement@53385338
Displaying FFDC information for wrapper hierarchy,
beginning from the Connection...
First Failure Data Capture information for
com.ibm.ws.rsadapter.jdbc.WSJdbcConnection@7c9e7c9e
com.ibm.ws.rsadapter.jdbc.WSJdbcConnection@7c9e7c9e
Transaction Manager global transaction status is
STATUS NO TRANSACTION (6)
Underlying Connection: oracle.jdbc.driver.LogicalConnection@3dfc3dfc
oracle.jdbc.driver.LogicalConnection@3dfc3dfc
Key Object:
[B@14f414f4
DataStoreHelper:
com.ibm.websphere.rsadapter.Oracle10gDataStoreHelper@3ebc3ebc
Connection Manager:
[ConnectionManager]@4ee24ee2
JNDI Name <FNGCDDS>
shareable <true>
ConnectionManager supports lazy association?
true
ConnectionManager supports lazy enlistment?
true
Handle is reserved? false
AutoCommit value tracked by handle: true
Detection of multithreaded access is:
DISABLED
Thread id:
null
Wrapper State:
ACTIVE
Parent wrapper:
null
Child wrapper:
null
# of Child Wrappers 1
Child wrappers:
com.ibm.ws.rsadapter.jdbc.WSJdbcStatement@53385338
ConnectionRequestInfo:
null
First Failure Data Capture information for
com.ibm.ws.rsadapter.spi.WSManagedConnectionFactoryImpl@63666366
Detection of multithreaded access is
DISABLED
Resource Adapter:
null
Hash Code:
-1131425938 (0xbc8fcf6e)
DataSource properties:
{enable2Phase=false, serverName=localhost, statementCacheSize=10, user=gcduser, dataStoreHelperClass=com.ibm.websphere.rsadapter.Oracle10gDataStoreHelper, URL=jdbc:oracle:thin:@localhost:1521:orcl, databaseName=orcl, selectMethod=direct, dataSourceClass=oracle.jdbc.pool.OracleConnectionPoolDataSource, password=******, portNumber=1521}
Database Type:
null
DataStoreHelper:
com.ibm.websphere.rsadapter.Oracle10gDataStoreHelper@3ebc3ebc
Description:
null
InternalDataStoreHelper:
[email protected]8
Log Writer:
null
Performance Monitoring Instrumentation:
com.ibm.ws.pmi.server.modules.J2CModule@46cc46cc
Statement Cache Size (maximum):
10
Transaction Branches are set to be Loosely Coupled:
false
Counter of fatal connection errors on ManagedConnections created by this MCF:
0
Validate existing connections on cleanup after a fatal connection error is detected?
true
ResetConnectionByBackendDatabase:
false
Backend id checking is:
true
JMSOnePhaseOptimization:
false
Reauthentication:
false
newDBConnectionValidationEnabled:
false
connectionRetriesDuringDBFailover:
100
connRetryDurationDuringDBFailover:
3000
Connection Factory Type:
com.ibm.ws.rsadapter.jdbc.WSJdbcDataSource
Listing PropertyChangeListeners:
First Failure Data Capture information for
com.ibm.ws.rsadapter.spi.WSRdbDataSource@34003400
DataSource Implementation Class Name:
oracle.jdbc.pool.OracleConnectionPoolDataSource
DataSource Name:
null
DataStoreHelper:
com.ibm.websphere.rsadapter.Oracle10gDataStoreHelper@3ebc3ebc
DataSource properties:
{enable2Phase=false, serverName=localhost, statementCacheSize=10, user=gcduser, dataStoreHelperClass=com.ibm.websphere.rsadapter.Oracle10gDataStoreHelper, URL=jdbc:oracle:thin:@localhost:1521:orcl, databaseName=orcl, selectMethod=direct, dataSourceClass=oracle.jdbc.pool.OracleConnectionPoolDataSource, password=******, portNumber=1521}
ONE PHASE ENABLED
Underlying DataSource Object: oracle.jdbc.pool.OracleConnectionPoolDataSource@39703970
oracle.jdbc.pool.OracleConnectionPoolDataSource@39703970
Counter of unique, modified DataSource configurations: 0
DynamicDSConfigManager
null
First Failure Data Capture information for
com.ibm.ws.rsadapter.spi.WSRdbManagedConnectionImpl@3f023f02
ONE PHASE ENABLED
Database Type:
null
Transaction State:
NO_TRANSACTION_ACTIVE
Statement Cache Size (maximum):
10
Key:
[B@14f414f4
Performance Monitoring Instrumentation:
com.ibm.ws.pmi.server.modules.J2CModule@46cc46cc
Log Writer:
null
Subject:
null
ManagedConnection:
WSRdbManagedConnectionImpl@3f023f02
Counter of fatal connection errors for the ManagedConnectionFactory as of the most recent getConnection on this ManagedConnection:
0
Default AutoCommit:
true
Current AutoCommit:
true
AutoCommit reported by the JDBC driver:
true
Current Isolation:
READ COMMITTED (2)
Isolation level has changed? :
false
Support isolation level switching:
false
Isolation reported by the JDBC driver:
READ COMMITTED (2)
Catalog, IsReadOnly, or TypeMap has changed? :
false
Default Holdability:
DEFAULT CURSOR HOLDABILITY VALUE (0)
Current Holdability:
DEFAULT CURSOR HOLDABILITY VALUE (0)
Holdability value has changed? :
false
Holdability reported by the JDBC driver:
DEFAULT CURSOR HOLDABILITY VALUE (0)
Thread ID:
null
Lazily enlisted in the current transaction? :
false
Underlying Connection Object: oracle.jdbc.driver.LogicalConnection@3dfc3dfc
oracle.jdbc.driver.LogicalConnection@3dfc3dfc
Underlying PooledConnection Object: oracle.jdbc.pool.OraclePooledConnection@64ec64ec
oracle.jdbc.pool.OraclePooledConnection@64ec64ec
SQLJ Default Context: null
null
Is statement caching enabled? :
true
Fatal connection error was detected? :
false
Currently cleaning up handles? :
false
Last ConnectionEvent sent for this ManagedConnection:
com.ibm.ws.rsadapter.spi.WSConnectionEvent@3f583f58
Connection Handle: null
Event ID: UNKNOWN CONNECTION EVENT CONSTANT (0)
Exception: null
Driver version:
10.2.0.3.0
Database version:
Oracle Database 10g Enterprise Edition Release 10.2.0.3.0 - Production
With the Partitioning, OLAP and Data Mining options
Connection Event Listeners:
com.ibm.ejs.j2c.ConnectionEventListener@6f306f30
Interaction Metrics:
com.ibm.ejs.j2c.ConnectionEventListener@6f306f30
Maximum Handle List Size: 15
Handle Count: 1
Handles:
com.ibm.ws.rsadapter.jdbc.WSJdbcConnection@7c9e7c9e
null
null
null
null
null
null
null
null
null
null
null
null
null
null
State Manager:
com.ibm.ws.rsadapter.spi.WSStateManager@6ec46ec4
XA Resource:
null
First Failure Data Capture information for
com.ibm.ws.rsadapter.spi.WSRdbSpiLocalTransactionImpl@7c827c82
Connection:
oracle.jdbc.driver.LogicalConnection@3dfc3dfc
ManagedConnection:
WSRdbManagedConnectionImpl@3f023f02
Detection of multithreaded access is:
DISABLED
ManagedConnectionMetaData:
null
Statement Cache:
com.ibm.ws.rsadapter.spi.CacheMap@6d486d48
Number of entries: 0
Maximum entries: 10
Number of buckets: 13
Maximum bucket size: 5
Number of discards: 0
BUCKET SIZE PREV NEXT
000 000 013 013
001 000 013 013
002 000 013 013
003 000 013 013
004 000 013 013
005 000 013 013
006 000 013 013
007 000 013 013
008 000 013 013
009 000 013 013
010 000 013 013
011 000 013 013
012 000 013 013
013 LRU 014
014 MRU 013
First Failure Data Capture information for
com.ibm.ws.rsadapter.spi.WSConnectionRequestInfoImpl@345e345e
extention DS properties =
null
extention DS properties key =
0
useHetrogeneous =
false
changable CRI =
false
optimizeForGetUseCloseUsage =
false
User Name:
null
Password:
null
Isolation Level:
READ COMMITTED (2)
Catalog:
null
Is Read Only?
null
Type Map:
null
Cursor Holdability:
DEFAULT CURSOR HOLDABILITY VALUE (0)
Config ID: 0
Hash Code:
0
Support isolation switching on connection:
false
NoEnlistment:
false
ShareWithCMPOnly:
false
Handle type:
java.sql.Connection
TrustedContext_name:
null
TrustedContext_realm:
null
TrustedContext_userSecToken:
null
TrustedContext_originalUser:
null
trustedContextIdentityAttributesAreSet =
false
First Failure Data Capture information for
com.ibm.ws.rsadapter.spi.WSManagedConnectionFactoryImpl@63666366
Detection of multithreaded access is
DISABLED
Resource Adapter:
null
Hash Code:
-1131425938 (0xbc8fcf6e)
DataSource properties:
{enable2Phase=false, serverName=localhost, statementCacheSize=10, user=gcduser, dataStoreHelperClass=com.ibm.websphere.rsadapter.Oracle10gDataStoreHelper, URL=jdbc:oracle:thin:@localhost:1521:orcl, databaseName=orcl, selectMethod=direct, dataSourceClass=oracle.jdbc.pool.OracleConnectionPoolDataSource, password=******, portNumber=1521}
Database Type:
null
DataStoreHelper:
com.ibm.websphere.rsadapter.Oracle10gDataStoreHelper@3ebc3ebc
Description:
null
InternalDataStoreHelper:
[email protected]8
Log Writer:
null
Performance Monitoring Instrumentation:
com.ibm.ws.pmi.server.modules.J2CModule@46cc46cc
Statement Cache Size (maximum):
10
Transaction Branches are set to be Loosely Coupled:
false
Counter of fatal connection errors on ManagedConnections created by this MCF:
0
Validate existing connections on cleanup after a fatal connection error is detected?
true
ResetConnectionByBackendDatabase:
false
Backend id checking is:
true
JMSOnePhaseOptimization:
false
Reauthentication:
false
newDBConnectionValidationEnabled:
false
connectionRetriesDuringDBFailover:
100
connRetryDurationDuringDBFailover:
3000
Connection Factory Type:
com.ibm.ws.rsadapter.jdbc.WSJdbcDataSource
Listing PropertyChangeListeners:
First Failure Data Capture information for
com.ibm.ws.rsadapter.spi.WSRdbDataSource@34003400
DataSource Implementation Class Name:
oracle.jdbc.pool.OracleConnectionPoolDataSource
DataSource Name:
null
DataStoreHelper:
com.ibm.websphere.rsadapter.Oracle10gDataStoreHelper@3ebc3ebc
DataSource properties:
{enable2Phase=false, serverName=localhost, statementCacheSize=10, user=gcduser, dataStoreHelperClass=com.ibm.websphere.rsadapter.Oracle10gDataStoreHelper, URL=jdbc:oracle:thin:@localhost:1521:orcl, databaseName=orcl, selectMethod=direct, dataSourceClass=oracle.jdbc.pool.OracleConnectionPoolDataSource, password=******, portNumber=1521}
ONE PHASE ENABLED
Underlying DataSource Object: oracle.jdbc.pool.OracleConnectionPoolDataSource@39703970
oracle.jdbc.pool.OracleConnectionPoolDataSource@39703970
Counter of unique, modified DataSource configurations: 0
DynamicDSConfigManager
null
+Data for directive [defaultadapter] obtained. =
==> Dump complete for com.ibm.ws.rsadapter.DiagnosticModuleForAdapter = Sun Feb 03 12:59:15 CST 2008
Any Ideas?
Thanks in advance.
Regards,
Rajan

SAP on solaris x86 or sparc

Hi,
Can you please let me know the advantages of running SAP on Solaris X86 or SPARC machines. Which is recommended?
Thanks
Joyce

> If the compnay has very few end users to work on SAP i.e. less than 50 users, then x86 is suited.
> FOr large ended systems that is for large number of users to work on SAP, SPARC is better choice.
> SPARC is recommended.
I'm sorry but this is simply not true.
x86_64 is VERY suited for big systems, we run x86_64 systems with 1000+ users, on Solaris and on Linux.
Solaris on x86_64 is a very good choice, a mature OS with lots of features (zones, ZFS...) running on affordable hardware.
SPARC is a RISC architecture, there are even drawbacks in performance if you use e. g. T-series systems (UltraSparc) for ABAP systems and databases (see Oracle Metalink ID 781763.1 - "Migration from fast single threaded CPU machine to CMT UltraSPARC T1 and T2 results in increased CPU reporting and diminished performance").
So it's a matter of taste and choice - and money.
Markus

Install Developer 9.0.4 On solaris x86

Hi All
we have installed oracle database 10g rel2 on solaris x86 then we are trying to install oracle application server forms and reports services standalone on the same machine but we have a problem
after running ./runInstaller we have an error
./runInstaller: /export/home/cd1/disk1/install/solaris/runInstaller: cannot execute
any one can help

Hi.
I've installed it on fedora, Red Hat as 2.1 and 3.0. Here are the instructions I followed:
http://www.oracle-base.com/articles/Linux/ArticlesLinux.php
I know they're not what you're looking for but they might give you some ideas.
Cheers
Tim...

Solaris X86

Hi guys
Can i use oracle 11g Solaris SPARC installation media on x86 solaris ? or do i have to use the linux instllation media .
thanks
AO

I see that this question is answered but if you are still following the thread I thought I might add the following info:
Solaris Operating System (x86-64)
http://www.oracle.com/technology/software/products/database/oracle10g/htdocs/10201solx8664soft.html
Get both 10201_database_solx86_64.zip and 10201_companion_solx86_64.zip.
Trying to install the companion later may involve rolling back patches so installing it up front is a good idea.
Oracle 10.2.0.4 is patch id 6810189
OPatch is patch id 6880880
January 2009 Critical Patch Update is patch id 7592346
742060.1 Release Schedule of Current Database Patch Sets
-- Per note above there will not be a 10.2.0.5 unless things change after Oracle buys Sun.
-- Per note above there will not be 11.1.0.6 and 11gR2 may be first 11g on Solaris/x86.
555579.1 10.2.0.4 Patch Set - Availability and Known Issues
786800.1 Critical Patch Update April 2009 Patch Availability Document for Oracle Products
756671.1 Oracle Recommended Patches -- Oracle Database
8362683.8 Bug 8362683 - 10.2.0.4 Generic Recommended Patch Bundle #4
I hope you found this helpful.

No place for bug reports?

I'm evaluating StarOffice both for my own use and recommendation to my clients. Today I encountered a clear bug -- an RTF file that other applications (incl. MS Word) open correctly but which causes StarOffice to crash. Looking on the Sun site I find no place for bug reports -- anyone who wants to report a bug must in effect pay for the privlege.
Seems like a serious problem and one which would make it impossible to recommend the suite to clients.
Will O'Neil

I've encountered a problem with StarOffice 8 where a certain few RTF files would cause StarOffice and the user's session to crash out to the login GUI. The problem manifested itself as such:
1. Start the StarOffice Write application
2. Open suspect RTF file, file loads and displays the first page of the document
3. Click the slider on the right side of the screen to page down to the next section of the document
At this point StarOffice crashes and you're presented with the CDE login screen.
Analysis:
This seemed to happen to only one of the 3 users using StarOffice. The same document opened by another user did not produce the same crash result.
Solution:
Deleted the .staroffice8 directory in the user's home directory and restarted StarOffice
Result:
Suspect document now loads and scrolls properly without crashing.
Hope this helps.

Deinstall on Solaris x86

not sure if this is the right place, but couldn't see one that was more germaine.
i just used dbca to remove a 10gR1 database from a system and then used runInstaller to remove the binaries. it hung up the system and ended up corrupting the mounted filesystem -- we had to do a umount and fsck to get it back and all the bad nodes were oracle nodes.
has anyone else had or heard of this kind of situation? is this a bug? did i do something wrong?
help?

We are doing work on converging the JVMs (Hotspot and JRockit). Solaris x86 is supported today for hotspot, and will be supported by the converged JVM as it is released.
As things stand right now, JRockit will not be supported on Solaris x86 until JRockit will be replaced by the converged JVM.

Network is down suddenly on my Solaris X86 box

Hi all,
I have been using Solaris X86 for a while. However, I found a strange problem when downloading large/many
files with FTP. For example, I ftp to my Solairs X86 box and try to download all my backup software to my local
notebook or PC. After about 10 mins, Solaris X86 box's network will be down suddenly without any error or
warning message.
I found this problem from Solaris8 to Solaris9 and the FTP server daemon I used included NcFTPd, vsftp and
even the default FTP daemon. I have tried two different hardwares. The only one possible reason is my
network (Intel 100 ServerPro something).
Does anyone have such a strange problem when downloading many/large files from your Solaris X86 box?
I also check the log file but found nothing.....:-(
Thinking to switch FreeBSD/Linux box for my FTP service. Please advice and thanks first!
Hsinan

This bug is common to the Intel Server 100 MBit Cards
The problem occurs on high net load.
You have to reboot to restart the card, since it is a complete
stop of the card.
You can try to put the card into another pci-slot, but this helps
only in rare cases.
I had to replace the card with a 3com 3c905b to have uninterrupted
transfers.
The Inteldualport cards seem to work to.

Bug report follow-up

is there a way to follow-up on a bug report that i submitted? i have the bug number, but would like to see if the report was understood, filled out properly and determine the status of the bug report.
thanks,
doug

They comment on bugs if actions were taken. Otherwise - don't expect any feedback.

Did you know that Google toolbar doesn't work properly in FF rc1? I have filed a bug report to Google about this

The Google toolbar doesn't recognize a left mouse click when selecting a 'suggestion'. It's OK using the keyboard, however. I have filed a bug report with Google, but as this is an important extension thought you should know.

See also: http://forums.adobe.com/message/4662367#4662367
-Noel

Bug Report: The keyboard focus doesn't automatical...

Bug Report: When a conversation window opens, the focus doesn't automatically land in the chat entry text field.
Since the new interface for Skype was introduced officially in Skype 7.0, there is a bug with the system/keyboard focus for a new conversation window. When Skype is in "Split Window View" and each new conversation automatically pops up in a separate window, the system/keyboard focus doesn't land in the chat entry edit field. Instead, the user has to press Shift+TAB a couple of times, to move it there and reply to the chat message received. This especially problematic for screen reader users, who rely on keyboard navigation. This mainly occurs when a new conversation is started with an incoming message, but it sometimes occurs when moving the focus out of that conversation window and later back in it again (while it is still opened).
Steps to reproduce it:
1. From "View" menu, activate the "Split Window View", if it is not already enabled.
2. From Tools -> Options -> IM & SMS -> IM settings, enable "Open a new window when I receive a new message in Split Window View", if it is not already enabled.
3. From Tools -> Options -> Advanced, activate "Enable accessible mode", if it is not already enabled.
4. Activate the "Save" button, to save the changes.
5. Close all windows, related to Skype. You may keep only the main window opened.
6. Tell someone to send you a chat message. When the message arrives, Move the system focus to the conversation window in question, preferably with Alt+TAB. The system/keyboard will not land in the chat entry edit field as it did in Skype 6.21 and earlier and as it should by default, but in some unknown place in the window.
7. Move the system/keyboard focus in the chat entry edit field and keep it there.
8. Switch to another window, preferably from another application.
9. With Alt+TAB, switch back to the window of the opened Skype conversation. There is a chance that the system/keyboard focus will not land in the chat entry edit field as it did in Skype 6.21 and earlier and as it should do by default, but again in some unknown place in the conversation window. But that is harder to reproduce.
Test environment:
- Operating system: Windows 8.1 Pro N, 64-bit, in Bulgarian with all locale settings set to "Bulgarian".
- Skype version: 7.0.0.102 for Desktop.

This is a known problem, but Skype have not given us an estimated time for a fix.
Traditionally, Skype updates have been roughly monthly, so we are due a new version sometime soon. Many of us here are hoping that is has a bunch of fixes for the UI, the focus problem being one of them.
Sean Ellis - uses Skype chat for serious work
Click here to read my blog post on Skype 7 and basic principles of GUI design

Solaris 9 x86 bug report - el_GR.ISO8859-7 & CDE

Similar Messages

Maybe you are looking for