The only explanation of why some Java EE API classes are stripped off methods implementations I can find is this JBos forum post: What's the cause of this exception: java.lang.ClassFormatError: Absent Code? which also provides some workarounds for these crippled API classes. The explanation offered was: When one compiles, they want to run as well. By the way, we have been promoting full set of Java EE APIs which can only be used for compilation - they are stripped off method details. That way, user can't take those artifacts and try to use it in runtime. Honestly, I don't see any logic in those statements. This is the only place any such explanation is offered. Yes only from this JBos forum post! There's no public...

Here's a list of common TCP ports. You can find a more complete list here: http://www.gasmi.net/docs/tcp.html . Port Number Service Description 21 FTP File Transfer Protocol 22 SSH Secure Shell 23 Telnet Telnet remote login 25 SMTP Simple Mail Transfer Protocol 70 gopher Gopher 79 finger Finger 80 HTTP Hyper Text Transfer Protocol (WWW) 88 Kerberos Kerberos authentication 94 tivoli Tivoli Object Dispatcher 110 pop3 Post Office Protocol Version 3 123 ntp Network Time Protocol 137 netbios NetBIOS Name Service 138 netbios NetBIOS Datagram 139 netbios NetBIOS Session 143 imap Internet Message Access Protocol 161 snmp Simple Network Management Protocol 162 snmptrap SNMP trap 194 irc Internet Relay Chat Protocol 389 ldap Lightweight Directory Access Protocol 443 https Secure HTTP 445 SMB MS Server Message...

The dev database keeps locking up because of failed login attempts. For a dev database, we really don't need such security measure. This is how to remove the limit. Log in as sysdba sqlplus sys@xe as sysdba Find out the profile for the user. SQL> select profile from dba_users where username ... Look at the current limits SQL> select resource_name, limit from dba_profiles... Increase the value for failed login attempts SQL> alter profile default limit failed_login_atte...

Query the dba_users view to find locked accounts. SQL> select username, account_status, lock_dat...

DBA_BLOCKERS displays a session if it is not waiting for a locked object but is holding a lock on an object for which another session is waiting. Column Datatype Description HOLDING_SESSION NUMBER Session holding a lock SQL> select * from dba_blockers; HOLDIN...

DBA_WAITERS shows all the sessions that are waiting for a lock. Column Datatype Description WAITING_SESSION NUMBER The waiting session HOLDING_SESSION NUMBER The holding session LOCK_TYPE VARCHAR2(26) The lock type MODE_HELD VARCHAR2(40) The mode held MODE_REQUESTED VARCHAR2(40) The mode requested LOCK_ID1 VARCHAR2(40) Lock ID 1 LOCK_ID2 VARCHAR2(40) Lock ID 2 SQL> set lin 120 SQL> select * from dba_wai... Or join the v$session view to find out who it is: select w.waiting_session, w.mode_requested, s.user...

You run an update and it hangs. Use this query to find out who's locking the table. select o.object_type, o.object_nam...

When you start sqlplus withoud SID, Oracle says that you connect to the default database you created during installation. What if I installed multiple databases and I forgot which one is default? Is there a way to find out which is the current default? I wasn't able to find an answer. But there are a couple of ways to change the default by setting a couple of environment variables. The bad news is: the variables are different depending on which platform you are on. Unix If you are on Unix and the database is local, set these two variables: export ORACLE_HOME=/app/oracle/product/10.2.0/db_1... If the database is remote, set TWO_TASK : export TWO_TASK=orcl Windows If you are on Windows, set LOCAL : set LOCAL=orcl Of course,...

Remember the times when you googled for solutions to your technical problems? How much time did you spend on wading through the zillions of links to find the ones that are of interest to you? Wouldn't you hope that you can find the answer right away the second time around? How many times were you forced to peruse hundreds of pages of documentation for a very specific need? Did you ever need to experiment with various alternatives because the documentation was vague? Wouldn't you prefer that a shortcut is available when the same thing is needed again? Xinotes is here to record your technical findings so that you won't have to go through the same process again when the problem reappears. Experience has taught us...

Query the tables user_tab_columns or all_tab_columns : select column_name, data_type, data_length from us...