During an ETL job sometimes bad data will sneak into your OLTP and needs to be searched out. You can adjust the step limit by querying the R_STEP table and then updating the associated row in the R_STEP_ATTRIBUTE table:

To acquire the id_step for the r_step_attribute update:
sql> select id_step from r_step where name = 'your_stepname';

To update the limit (X = step limit, Y = id_step from above):
sql> update r_step_attribute set value_num=X where id_step=Y and code='limit';

Tip based on the ETL toolkit found at http://kettle.pentaho.org/.

Thanks to McG for the tip.

If you've got another service (e.g., tomcat) fighting for port 8080, you can change the port Oracle uses with the following calls:

-- change HTTP port from 8080 to 8083
call dbms_xdb.cfg_update(updateXML(dbms_xdb.cfg_get(), '/xdbconfig/sysconfig/protocolconfig/httpconfig/http-port/text()', 8083));

-- change FTP port from 2100 to 2111
call dbms_xdb.cfg_update(updateXML( dbms_xdb.cfg_get(), '/xdbconfig/sysconfig/protocolconfig/ftpconfig/ftp-port/text()' , 2111));

-- refresh settings
exec dbms_xdb.cfg_refresh;

Tip borrowed from an article by red-database-security.com.

To determine the size of your Oracle database you need to run a few queries and add up the numbers:

sql> select sum(bytes)/1024/1024 from dba_data_files;
sql> select sum(bytes)/1024/1024 from v$log;

Those two queries will tell you how big it is, also if you're in archive log mode, you'll generate files in your archive log destination. Run this query to determine its location:

sql> select * from v$parameter where name = 'log_archive_dest';

If you get something back, you need to add that to the mix as well.

Run the following query:

SELECT s.username, s.program, s.logon_time
FROM v$session s, v$process p, sys.v_$sess_io si
WHERE s.paddr = p.addr(+)
AND si.sid(+) = s.sid
AND s.type = 'USER';